Can Landing AI derive a value when the answer is not printed in the document?
Landing AI derived the requested value in this scenario. The invoice shows DISTANCE 450 miles and FUEL RATE £0.18 per mile; the JSON returns fuel_cost as GBP 81.00, and the document text does not contain 81.00. The playground screen shows the same result beside a one-field schema.
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 counts this row.
Derived value from two present valuesPassEvidence
{ "data": { "fuel_cost": "£81.00" }, "extractionMetadata": { "fuel_cost": { "value": "£81.00", "ranges": [ { "start": 316, "end": 326 }, { "start": 338, "end": 352 } ] } }, "extract_id": "extract-01m4ann5yp6j7hhn8ckkk14be2", "parse_run_id": "parse-01m4anmhtay7pt731hezb4fyrq", "created_at": "2026-10-07T07:53:48.821Z" }
Copied from Proof 1 · Output file (text), lines 1–11
Open the text file ↗Its contents are printed above, under What the tool returned.
Open the text file ↗| ✓ | Expected: The computed value itself, not one of the input numbers.Found: The JSON returns GBP 81.00 for fuel_cost, and the document text does not contain 81.00. |
Landing AI was compared with the invoice, the returned JSON, and the playground screen. The invoice shows DISTANCE 450 miles and FUEL RATE £0.18 per mile once each; the JSON returns fuel_cost as GBP 81.00, and the value does not appear in the document.
Two source spans. The field is linked to two source spans, which fits two operands rather than a stated total.
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 row says which 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 row 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 | Landing AI → |
Global scenario definition → · Global capability definition → · Landing AI 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.