Can Nanonets show where a value came from in the document?
Nanonets traced the returned subtotal to page 2, where GBP 6,103.00 is highlighted in the totals block. The exported page number was 2, and the preview highlight sat on the returned value rather than the neighboring totals.
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.
Pointer to where the value sitsPassEvidence
{ "subtotal": "6,103.00", "page_number": 2 }
Copied from Proof 1 · Output file (JSON), lines 1–4
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 points to the document location that matches the returned value.
- Whether the location is attached to the value it actually returned, not to a different one.
- Whether the tool gives a source location rather than only repeating the value or naming the document.
| ✓ | Found: A page pointer resolved to the page containing 6,103.00. |
The tool returned a page pointer for the subtotal, and it resolved to page 2 where 6,103.00 appears. The page-number field also pointed to the printed page label, showing the result came from source links rather than a default guess.
Page label also highlighted. The page-number field linked to the printed page label, while the subtotal field linked to the subtotal value on page 2. The graded result depends on the subtotal link, not the page label.
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 | Source Grounding → | |
| Scenario | Trace a value to its location → | |
| Tool | Nanonets → |
Global scenario definition → · Global capability definition → · Nanonets 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.