Can LlamaParse derive a value that appears nowhere in the document?
LlamaParse passed this derived-value task. It read the two page-1 operands and returned £81.00; the derived field had no citation, and the source contains no 81.00.
1 of 1 test case passed
Every test case in this scenario has a result.
The test case
Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above is based on this test case.
Derived value from two present valuesPassEvidence
{ "type": "object", "properties": { "distance_miles": { "type": "string", "description": "The distance of the route, in miles, as stated on the invoice." }, "fuel_rate_per_mile": { "type": "string", "description": "The fuel rate per mile, labelled 'FUEL RATE' on the document, including currency. The value may be a whole number or a decimal number - if the number in the document is in decimal form, the extraction should give the value in decimal, exactly as mentioned in the document." }, "total_fuel_cost": { "type": "string", "description": "The total fuel cost - calculated as the distance in miles multiplied by the fuel rate per mile. This value does NOT appear anywhere in the document; you must compute it from distance_miles x fuel_rate_per_mile." } }, "required": ["distance_miles", "fuel_rate_per_mile", "total_fuel_cost"] }
"distance_miles": "450 miles", "fuel_rate_per_mile": "£0.18 per mile", "total_fuel_cost": "£81.00"
Extraction output: the operands and returned total
Copied from Output file (JSON), lines 9–13 · an excerpt
Open the whole JSON file ↗Source excerpt · partial file · response 1
"extract_result": { "distance_miles": "450 miles", "fuel_rate_per_mile": "£0.18 per mile", "total_fuel_cost": "£81.00" },
Copied from Output file (JSON), lines 9–13 · an excerpt
| ✓ | Expected: A computed value from two present values, not a refusal or a copied input.Found: It returned £81.00 from the two page-1 values, and the result is absent from the source. |
The test required one unambiguous arithmetic result from two labelled values, with the result absent from the document. LlamaParse returned £81.00 from 450 miles and £0.18 per mile, and the document contains no 81.00.
Citation split. The two source values were cited on page 1, while the computed total had no citation and only a confidence score.
Configuration and setup
How this tool was set up for the run and what the test needed in place. Each row is a fact from the run's records; a fact the records do not hold is left out, not guessed.
How this scenario is graded
How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.
Each test case gets one result per tool: Pass, Fail or Not gradable. A test case we haven't run yet shows Untested. There are no partial results.
- Pass: the tool did everything the test expected, and nothing it said contradicts the correct answer.
- Fail: at least one expected behaviour clearly didn't happen; the test case's result says which one and quotes the tool.
- Not gradable: our evidence couldn't settle the outcome (for example a record we needed is missing). It is never counted as a fail, and the test case's result says what's missing.
Where this sits in the benchmark
This page is one cell of a larger study: one tool, one scenario. Only this benchmark's frame appears here.
| Level | Name | Scope |
|---|---|---|
| Benchmark | Structured Document Extraction → | 19 scenarios · 10 tools |
| Capability | Field Extraction → | |
| Scenario | The value must be derived → | |
| Tool | LlamaParse → |
Global scenario definition → · Global capability definition → · LlamaParse product page →
History of this result
What has happened to this result since it was first published. Runs and grades are never overwritten: a retest or a re-grade publishes a new result and keeps the earlier one readable.
Act on this result
Nothing filed here edits the run or the grade. A challenge opens a review, and a review can produce a new run or a re-grade — which becomes the current result and leaves this one in the history.
You run the same kind of test against your own setup and get the same behaviour.
Agree →Yours behaves differently. Tell us what you got, with a screenshot if you have one.
Disagree →Something here is wrong — a reference value, a transcription, a grade.
Report an issue →Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.
Vendor notice →The same record is available as structured data through the AI Demos MCP server, with the counts, the coverage and every per-test-case reason carried as fields.
Verify the proof files
These files support this result. Open a file to inspect the original evidence.
File fingerprints (SHA-256)
A fingerprint identifies the exact file used for this result.