Can Docsumo extract a repeated set from one page?
Docsumo extracted the invoice’s three line items with the right values attached to each item. It excluded the subtotal, VAT and total rows from the extracted set.
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
{ "Table": { "line_items": { "type": "table", "columns": [ { "name": "description" }, { "name": "item_code" }, { "name": "quantity" }, { "name": "unit_price" }, { "name": "amount" } ] } } }
{ "description": { "position": [159, 5058, 1495, 5085], "value": "Dosing pump, 240V", "review_required": false, "confidence": 1 }, "item_code": { "position": [159, 5058, 1495, 5085], "value": "DP-2210", "review_required": false, "confidence": 1 }, "quantity": { "position": [159, 5058, 1495, 5085], "value": 2, "review_required": false, "confidence": 1 }, "unit_price": { "position": [159, 5058, 1495, 5085], "value": 340, "review_required": false, "confidence": 1 }, "amount": { "position": [159, 5058, 1495, 5085], "value": 680, "review_required": false, "confidence": 1 }
Extraction JSON: three item rows with descriptions, codes, quantities, unit prices and amounts
Copied from Output file (JSON), lines 5–60
Open the JSON file ↗{ "description": { "position": [158, 5129, 1493, 5149], "value": "Chemical feed tubing, 10m coil", "review_required": false, "confidence": 1 }, "item_code": { "position": [158, 5129, 1493, 5149], "value": "CT-1040", "review_required": false, "confidence": 1 }, "quantity": { "position": [158, 5129, 1493, 5149], "value": 3, "review_required": false, "confidence": 1 }, "unit_price": { "position": [158, 5129, 1493, 5149], "value": 48, "review_required": false, "confidence": 1 }, "amount": { "position": [158, 5129, 1493, 5149], "value": 144, "review_required": false, "confidence": 1 }
Copied from Output file (JSON), lines 62–117
{ "description": { "position": [159, 5194, 1495, 5215], "value": "Inline flow sensor", "review_required": false, "confidence": 1 }, "item_code": { "position": [159, 5194, 1495, 5215], "value": "FS-3302", "review_required": false, "confidence": 1 }, "quantity": { "position": [159, 5194, 1495, 5215], "value": 1, "review_required": false, "confidence": 1 }, "unit_price": { "position": [159, 5194, 1495, 5215], "value": 215, "review_required": false, "confidence": 0.5 }, "amount": { "position": [159, 5194, 1495, 5215], "value": 215, "review_required": false, "confidence": 0.5 }
Copied from Output file (JSON), lines 119–174
| ✓ | Expected: Return all three genuine items once, keeping each description, item code, quantity, unit price and amount with the correct item.Found: Invoice and output each show three items: dosing pump, 2 at 340, amount 680; chemical feed tubing, 3 at 48, amount 144; inline flow sensor, 1 at 215, amount 215. |
The requirement was to preserve which values belong to which item, not just count rows. The configured columns matched the invoice, and no item was dropped, duplicated or given another item’s values.
Sensor price confidence. The inline flow sensor’s unit price and amount were correct at 215 each, yet received confidence 0.5. Every other field received 1.
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 | Docsumo → |
Global scenario definition → · Global capability definition → · Docsumo 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.