Can FutureSmart Document Intelligence keep one array when a set continues across a page break?
FutureSmart Document Intelligence returned one ordered line_items array of ten objects across the page break, with no duplicate at the boundary and no second array. The visible proof showed items 1-4 in the first frame and items 5-10 in the later screenshot.
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
{ "summary": "This invoice from Meridian Retail Group to Blackwood Distribution LLC details the supply of various retail fixtures and store equipment. The document lists ten line items including shelving, checkout counters, and scanning equipment, totaling £6,591.24 including VAT.", "document_type": "invoice", "line_items": [ { "amount": 1008, "quantity": 12, "unit_price": 84, "description": "Retail Shelving Unit - Steel, 5-Tier" }, { "amount": 930, "quantity": 3, "unit_price": 310, "description": "Checkout Counter - Laminate Top" }, { "amount": 273, "quantity": 6, "unit_price": 45.5, "description": "Security Tag Deactivator - Handheld" }, { "amount": 648, "quantity": 4, "unit_price": 162, "description": "Price Label Printer - Thermal" }, { "amount": 304, "quantity": 8, "unit_price": 38, "description": "Shopping Basket - 20L, Set of 10" }, { "amount": 1080, "quantity": 2, "unit_price": 540, "description": "Storeroom Pallet Racking - 4-Bay" }, { "amount": 580, "quantity": 10, "unit_price": 58, "description": "Barcode Scanner - Wireless" }, { "amount": 330, "quantity": 15, "unit_price": 22, "description": "Receipt Paper Roll - Case of 50" }, { "amount": 570, "quantity": 6, "unit_price": 95, "description": "Mannequin - Adjustable, Full Body" }, { "amount": 380, "quantity": 5, "unit_price": 76, "description": "Display Signage Kit - Window Set" } ] }
Copied from Proof 1 · Output file (JSON)
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 returns the whole repeated set as one array.
- Whether it avoids splitting the set into separate arrays at the boundary.
- Whether it avoids dropping members that appear after the boundary.
- Whether it avoids duplicating members at the boundary.
- Whether each member remains associated with the correct record across the full set.
| ✓ | Found: One ordered array contains all 10 line items, with no duplicate or split at the page break. |
The extraction returned one ordered array of 10 line items across the page break, and the page-two screenshot matches the same sequence. No boundary item is duplicated or split.
No serial-number field. The returned objects have no serial-number field, so item order is the only positional signal in the array.
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 | 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.