Can Nanonets carry corrected data downstream?
Nanonets passes this scenario. In the tested case, the corrected receipt number appears in the product’s delivery path: the result grid shows RHS-99999, the Download menu is open on that grid, and the exported JSON carries RHS-99999 with the other receipt values.
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.
Correction survives the delivery pathPassEvidence
“Attachment TC1_TC4_TC5A_basel... PDF; 'Extract the following fields from this document and return the result as JSON: receipt_number, subtotal, tax, total_due.'”
{ "receipt_number": "RHS-99999", "subtotal": "$85.00", "tax": "$5.10", "total_due": "$90.10" }
Copied from Proof 1 · Output file (text), lines 1–6
Open the text file ↗Its contents are printed above, under What the tool returned.
Open the text file ↗| ✓ | Expected: The delivery path carries the corrected value.Found: The open Download menu leads to JSON export carrying RHS-99999. |
The delivery path was checked after the receipt number correction. The corrected grid was open, the Download menu was available on it, and the exported JSON carried RHS-99999 with the other receipt values.
Closing message mismatch. The closing message still shows the original receipt number while the result grid and JSON export show the corrected one.
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 | Review and Correction → | |
| Scenario | Corrected data goes downstream → | |
| 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.