Can FutureSmart Document Intelligence derive a value that appears nowhere but follows from other values?
FutureSmart Document Intelligence correctly derived the value from present inputs. The output returned total_fuel_cost 81 for distance_miles 450 and fuel_rate__per_mile 0.18, and the string "81" does not appear anywhere in the three-page source.
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
{ "summary": "This invoice from Calderwood Freight Services details the freight and handling charges for a shipment from Leeds to Portsmouth. The consignment was successfully delivered and signed for on 07 March 2026 with no reported damage or exceptions.", "document_type": "invoice", "distance_miles": 450, "total_fuel_cost": 81, "currency": "GBP", "fuel_rate__per_mile": 0.18, "file_name": "Calderwood_Freight_S66_S67_S72.pdf" }
Copied from Proof 1 · Output file (JSON), lines 1–9
Open the JSON file ↗Its contents are printed above, under What the tool returned.
Open the JSON file ↗These are scenario-level criteria. Each test case's Expected and Found are listed separately.
- Whether the tool derives a requested field from values already present in the document.
- Whether it returns the inferred value when the schema asks for something not stated directly.
- Whether it distinguishes a computed answer from a value copied verbatim from the page.
| ✓ | Found: The tool returned total_fuel_cost 81, matching 450 × 0.18. |
The invoice shows distance 450 miles and fuel rate £0.18 per mile, and the document text contains no 81. The extracted total fuel cost is 81, so the tool computed the answer rather than copying it from the page.
Decimal truncation worked around. An earlier number field had truncated 0.18 to 0; making the field description explicit about decimals worked around that. The derived total stayed correct in both runs.
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 | FutureSmart Document Intelligence → |
Global scenario definition → · Global capability definition →
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.