Can LlamaParse keep a set together when it continues across a page break?
LlamaParse kept all ten invoice line items together in one array across the page break. It retained the six items from page one and four from page two, with no boundary duplicate and all 40 values correct.
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.
Set continues past a page boundaryPassEvidence
- properties › line_items › description
- Every line item in the invoice table, covering every row across both pages
- properties › line_items › items › properties
- { "description": { "type": "string", "description": "The description of the line item" }, "quantity": { "type": "string", "description": "The quantity of the line item" }, "unit_price": { "type": "string", "description": "The unit price of the line item" }, "amount": { "type": "string", "description": "The amount of the line item" } }
- required
- ["line_items"]
Show the whole file (1 KB)
{ "type": "object", "properties": { "line_items": { "type": "array", "description": "Every line item in the invoice table, covering every row across both pages", "items": { "type": "object", "properties": { "description": { "type": "string", "description": "The description of the line item" }, "quantity": { "type": "string", "description": "The quantity of the line item" }, "unit_price": { "type": "string", "description": "The unit price of the line item" }, "amount": { "type": "string", "description": "The amount of the line item" } } } } }, "required": ["line_items"] }
{ … "extract_result": { "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" } ] }, … }
Extraction output: one array of ten items, with no duplicate at the page break.
Copied from Output file (JSON), lines 10–71
Open the JSON file ↗| ✓ | Expected: One array containing the invoice’s ten line items, including those on page two, with none missing or duplicated at the page break.Found: It returned one array of ten items for the invoice’s ten rows, in order, without duplicates; 40 of 40 values matched the printed table. |
The requested set had to remain intact across both pages. Schema-driven extraction produced one array containing the invoice’s ten items in order, without a boundary duplicate; all 40 returned values matched the 40 printed values.
Reported confidence. The results panel reported at least 90% confidence for each of the 40 extracted line-item values.
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 | Nested & Repeated Fields → | |
| Scenario | The set continues across a page break → | |
| Tool | LlamaParse → |
Global scenario definition → · Global capability definition → · LlamaParse 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.