Can LlamaParse extract values from a document with digital and scanned pages?
LlamaParse extracted the requested values from a document mixing digital and scanned pages. It returned all five values correctly, including two found only on the scanned page.
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.
Values on both digital and scanned pagesPassEvidence
- properties
- { "invoice_reference": { "type": "string", "description": "The invoice reference number printed on the invoice" }, "order_reference": { "type": "string", "description": "The order reference the invoice relates to" }, "vehicle_registration": { "type": "string", "description": "The registration plate of the delivery vehicle" }, "received_by": { "type": "string", "description": "The name of the person who received the delivery" }, "total_due": { "type": "string", "description": "The total amount due on the invoice, including the currency symbol" } }
- required
- ["invoice_reference", "order_reference", "vehicle_registration", "received_by", "total_due"]
Show the whole file (1 KB)
{ "type": "object", "properties": { "invoice_reference": { "type": "string", "description": "The invoice reference number printed on the invoice" }, "order_reference": { "type": "string", "description": "The order reference the invoice relates to" }, "vehicle_registration": { "type": "string", "description": "The registration plate of the delivery vehicle" }, "received_by": { "type": "string", "description": "The name of the person who received the delivery" }, "total_due": { "type": "string", "description": "The total amount due on the invoice, including the currency symbol" } }, "required": ["invoice_reference", "order_reference", "vehicle_registration", "received_by", "total_due"] }
{ … "extract_result": { "invoice_reference": "HIS-4402", "order_reference": "FWT-PO-2291", "vehicle_registration": "LR19 KVM", "received_by": "J. Whitlock", "total_due": "£1,246.80" }, … }
Extraction output: five requested values returned
Copied from Output file (JSON), lines 9–15
Open the JSON file ↗| ✓ | Expected: Return all requested values from the digital and scanned pages accurately.Found: It returned five correct values. The total due was £1,246.80 in both the document and the output. |
The test required values from both page types. LlamaParse returned all five correctly, including the two available only on the image-only page, so the result is a pass.
Confidence note. In the five-field result, the app marked three fields below 90% confidence, although all five values were correct.
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 | OCR → | |
| Scenario | A document mixing digital and scanned pages → | |
| 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.