Does FutureSmart Document Intelligence keep a document answer separate from extracted data?
FutureSmart Document Intelligence passed this scenario. It gave the IFSC code and then said it came from reading the document directly, not from a separate extracted metadata field.
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.
Answer outside the schema, attributedPassEvidence
Input 1: “What is the IFSC code for this account?”
Input 2: “Is the IFSC code part of the extracted data for this document, or did you get that from reading the document directly?”
Response 1 answers Input 1.
Response 2, the final response, answers Input 2.
The IFSC code was obtained by reading the document directly. It appears in the statement's extracted body text, but it is not included as a separate extracted metadata field.
Transcribed from Proof 3 · Screenshot
Every message the tool sent, in order (2)
- Response to input 1
The IFSC code is SCBL0036091.
- Final response
The IFSC code was obtained by reading the document directly. It appears in the statement's extracted body text, but it is not included as a separate extracted metadata field.
| ✓ | Expected: It distinguishes: either it says the fact is not in extracted data, or it answers and says the answer came from the document.Found: It returned the code and said it came from reading the document directly, not from a separate extracted metadata field. |
It is a pass because the product returned the code shown in the document and, when asked, said it came from reading the document directly rather than from a separate extracted metadata field.
Sources link only. The first answer includes a sources link but no attribution sentence; the attribution appears only in the second turn.
Source summary balance. The source summary reports a closing balance of 116,149.46 INR.
The extracted-fields settings screen is not shown; the field list is supported by the setup card and the product's second answer.
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 | Querying → | |
| Scenario | The answer was never in the schema → | |
| 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.