Can LlamaParse extract a repeated set of records correctly?
LlamaParse handled the repeated set correctly. It returned all three records with the right values, and the per-value citations stayed in separate rows, so nothing was bound to the wrong record.
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.
Repeated set with correct associationPassEvidence
{ … "extract_result": { "line_items": [ { "description": "Dosing pump, 240V", "item_code": "DP-2210", "quantity": "2", "unit_price": "£340.00", "amount": "£680.00" }, { "description": "Chemical feed tubing, 10m coil", "item_code": "CT-1040", "quantity": "3", "unit_price": "£48.00", "amount": "£144.00" }, { "description": "Inline flow sensor", "item_code": "FS-3302", "quantity": "1", "unit_price": "£215.00", "amount": "£215.00" } ] }, … }
Job record: three extracted line items with matching page-3 citations
Copied from Output file (JSON), lines 10–32
Open the JSON file ↗| ✓ | Expected: Every record with the right values and the right record-to-field pairing.Found: All three members returned, with the right values on each row and no extras or omissions. |
It is a pass, not a fail: all three members returned, all fifteen values matched the page, and each record's citations stayed in its own row, so no value was bound to the wrong record.
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 | A repeated set of records → | |
| 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.