Can Nanonets aggregate a value across multiple documents?
Nanonets combined the amounts due from all three documents into the expected total of 474.93. The calculation left out no document and added no value from outside the set.
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 is based on this test case.
Total across every documentPassEvidence
“What is the total of total_due summed across all three documents? Return the result as JSON.”
Nothing further is required for the original request: the summed total_due was already calculated and returned as JSON. If continuing, the next step would only be to confirm or reuse the result {"total_total_due":474.93}. المصدر
Transcribed from Proof 1 · Screenshot
- total_total_due
- 474.93
Show the whole file (1 KB)
{ "total_total_due": 474.93 }
| ✓ | Expected: A total of 474.93 from the product’s extracted amounts across all three documents, with none omitted and no outside values added.Found: It returned 474.93; the reference sum of its extracted amounts was 474.93. It did not refuse the request. |
The task chat returned a total equal to the sum of Nanonets’ own extractions across the three intended documents. The boiler-inspection receipt’s 90.10 contribution is accounted for by subtraction; the screenshot does not show its extracted amount.
Extra word after JSON. The final chat answer appended a stray Arabic word after the JSON; the returned value was unchanged.
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 test case's result says which one 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 test case's result 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 | Aggregate across documents → | |
| 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.