Does LlamaParse treat a Total row as a non-member?
LlamaParse returned only the five genuine line items and left out the Total row. The returned rows matched the invoice rows, and the UI showed the same five rows with no Total row and page-1 citations.
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.
Total row is not a memberPassEvidence
"status": "COMPLETED", "error_message": null, "extract_result": { "line_items": [ { "description": "Retail Shelving Unit - Steel, 5-Tier", "quantity": "6", "unit_price": "84.00", "amount": "504.00" }, { "description": "Checkout Counter - Laminate Top", "quantity": "2", "unit_price": "310.00", "amount": "620.00" }, { "description": "Security Tag Deactivator - Handheld", "quantity": "4", "unit_price": "45.50", "amount": "182.00" }, { "description": "Price Label Printer - Thermal", "quantity": "3", "unit_price": "162.00", "amount": "486.00" }, { "description": "Shopping Basket - 20L, Set of 10", "quantity": "5", "unit_price": "38.00", "amount": "190.00" } ]
Result record: five extracted rows with page-1 citations
Copied from Output file (JSON), lines 7–41
Open the JSON file ↗| ✓ | Expected: Return only genuine members, with count separate from membership.Found: Five genuine line items came back, and the Total row was omitted. |
The tool’s response is printed above, under What the tool returned. Show this screenshot
Open original ↗It was a pass because the tool returned only real rows and left out the Total lookalike. Five genuine line items came back, and they matched the invoice rows.
Page-1 citations. Every returned field had a page-1 citation with a bounding box on the submitted document.
Only the agentic web-app tier was tested; other tiers and the API are outside this result.
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 contains a non-record → | |
| 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.