File size: 2,556 Bytes
af8e2e7 eacf9d5 af8e2e7 739fb8d af8e2e7 739fb8d 0f3b054 739fb8d af8e2e7 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 | ---
task_categories:
- question-answering
language:
- en
tags:
- finance
- search
- benchmark
size_categories:
- n<1K
configs:
- config_name: historical-lookup
data_files:
- split: public
path: historical-lookup.jsonl
- config_name: multi-hop-lookup
data_files:
- split: public
path: multi-hop-lookup.jsonl
- config_name: live-lookup
data_files:
- split: public
path: live-lookup.jsonl
---
# Finance Search
The public sample of the OpenBenchmarks finance search benchmark, which measures how well a search API helps an agent answer a finance professional's questions. The agent, prompt, search budget and grader are held fixed; only the search API changes. This sample is published so the question format and a harness can be checked end to end. Results on it are not leaderboard scores.
## Configurations
| Configuration | Rows | Task |
|---|---:|---|
| `historical-lookup` | 10 | One published figure for a named entity and period; one well-aimed search should find it. |
| `multi-hop-lookup` | 5 | Several published facts combined: a peer comparison, a trend, a result against guidance. |
| `live-lookup` | 6 | A price at a given moment, asked shortly after it: 3 stocks and 3 coins. |
Each configuration has one split named `public`.
## Fields
`historical-lookup` and `multi-hop-lookup`:
- `id`: question id.
- `question`: the question as asked, with named entities and absolute dates.
- `answer`: the reference answer. Where it ends with "Wrong:", the listed values are the expected wrong answers.
- `tolerance`: how close a numeric answer must be.
- `area`: one of company results, banks and insurers, macro and policy, small and international, markets.
`live-lookup`:
- `id`, `asset` (`equity`, `crypto`), `name`, `ticker`.
- `query_template`: the query a search API receives once filled in: `<name> (<ticker>) closing price {{date}}`
for stocks (that day's official close) and `<name> (<ticker>) price {{date}} {{time}}` for coins
(time in UTC).
## Live lookup
Live lookup measures freshness: how soon a new price reaches a search API's results. In the benchmark each item is
asked shortly after a moment that has just passed and graded against market data pulled afterwards, so a live answer
only exists once that moment has passed. These rows carry the items and the query format, without answers.
## Grading
An answer is correct only if every part the question asks for is right within its tolerance. A hedged answer counts
only if its committed value is right.
## License
No license is assigned yet.
|