Can FutureSmart Document Intelligence extract a plainly labelled field that appears once in ordinary digital text?
FutureSmart Document Intelligence passed this plain-field extraction case. The output and the document overview both returned the receipt number as RHS-70234, and the receipt text shows a different nearby identifier.
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.
Plainly-labelled scalar fieldPassEvidence
{ "summary": "This document is a service receipt from Riverside Home Services for a boiler annual inspection performed for Mr. Grant Sullivan. It details the service provided, the subtotal, tax, and the final total amount due.", "document_type": "receipt", "receipt_number": "RHS-70234", "subtotal": "$85.00", "tax": "$5.10", "currency": "USD", "total_due": "$90.10", "file_name": "Baseline_receipt.pdf" }
JSON output: receipt number and totals
Copied from Output file (JSON), lines 1–10
Open the JSON file ↗| ✓ | Expected: The value itself, correctly typed.Found: The receipt number is returned as the text RHS-70234, and the overview shows the same value. |
The tool’s response is printed above, under What the tool returned. Show this screenshot
Open original ↗It returned the requested receipt number as text, and the nearby licence number was a different identifier. That matches the one-field request.
Tax stayed textual. Tax is returned as the text "$5.10", not a number.
Other totals matched. Subtotal $85.00 and total $90.10 also match the receipt.
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 is directly available → | |
| 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.