Can FutureSmart Document Intelligence read a cleanly scanned document?
FutureSmart Document Intelligence returned the OCR text from the cleanly scanned document. It returned the as-found bias, -0.037 psu, for certificate C-77413; separately, the scanned certificate was the top search hit.
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.
Fact that exists only as pixelsPassEvidence
“What as-found bias is recorded on calibration certificate C-77413?”
The as-found mean bias recorded on calibration certificate C-77413 is **-0.037 psu**.
Text transcript of search and chat responses for the certificate question
Copied from Output file (text), lines 112–113 · an excerpt
Open the whole text file ↗Source excerpt · partial file · response 1
status: 200 answer: The as-found mean bias recorded on calibration certificate C-77413 is **-0.037 psu**.
Copied from Output file (text), lines 112–113 · an excerpt
| ✓ | Expected: The fact should come back from the scanned document, or the tool should say it yielded no text.Found: It returned the as-found bias, -0.037 psu, for certificate C-77413, and the answer did not shift to the as-left -0.004 psu beside it. |
The tool’s response is printed above, under What the tool returned. Show this screenshot
Open original ↗The chat answer gave the as-found bias from the certificate, and the same value appears in the extracted certificate text. That matches the clean-scanned-document task.
As-found stayed put. It returned the as-found bias and did not switch to the as-left value beside it.
Certificate text matched. It reproduced the certificate text, including the four-point results table.
Top result was unique. The chat results page showed 27 sections, and only the certificate scored 1.0000.
Only one scanned page was tested, so the result does not show OCR accuracy in general.
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 | Managed RAG → | 15 scenarios · 8 tools |
| Capability | Data Ingestion → | |
| Scenario | A cleanly scanned document → | |
| 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.