Can Nanonets keep one array across a page break?
Nanonets kept one array across the page break. The output has ten objects in one top-level array, with no second array and no repeated member at the boundary. The invoice shows items 1-6 on page 1 and 7-10 on page 2, and the result screen shows the same single table numbered 1 to 10.
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.
Set continues past a page boundaryPassEvidence
“Extract the following field from this document and return the result as JSON: line_items…”
[ { "description": "Retail Shelving Unit - Steel, 5-Tier", "quantity": 12, "unit_price": "84.00", "amount": "1,008.00" }, { "description": "Checkout Counter - Laminate Top", "quantity": 3, "unit_price": "310.00", "amount": "930.00" }, { "description": "Security Tag Deactivator - Handheld", "quantity": 6, "unit_price": "45.50", "amount": "273.00" }, { "description": "Price Label Printer - Thermal", "quantity": 4, "unit_price": "162.00", "amount": "648.00" }, { "description": "Shopping Basket - 20L, Set of 10", "quantity": 8, "unit_price": "38.00", "amount": "304.00" }, { "description": "Storeroom Pallet Racking - 4-Bay", "quantity": 2, "unit_price": "540.00", "amount": "1,080.00" }, { "description": "Barcode Scanner - Wireless", "quantity": 10, "unit_price": "58.00", "amount": "580.00" }, { "description": "Receipt Paper Roll - Case of 50", "quantity": 15, "unit_price": "22.00", "amount": "330.00" }, { "description": "Mannequin - Adjustable, Full Body", "quantity": 6, "unit_price": "95.00", "amount": "570.00" }, { "description": "Display Signage Kit - Window Set", "quantity": 5, "unit_price": "76.00", "amount": "380.00" } ]
Copied from Proof 1 · Output file (JSON), lines 1–62
Open the JSON file ↗Its contents are printed above, under What the tool returned.
Open the JSON file ↗| ✓ | Expected: One array with all members and no duplicate at the page break.Found: The output has one top-level array with ten members in order; the boundary item is not repeated and there is no second array. |
The extractor returned one array with all ten line items in document order, with no duplicate at the page break and no second array. The invoice shows the split across pages, and the result screen shows the same 1-to-10 table.
Number formatting. The prices and amounts are shown without the currency sign, and quantity is shown as a number. The values still match the invoice table.
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 | Nested & Repeated Fields → | |
| Scenario | The set continues across a page break → | |
| 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.