Can LlamaParse return a value that is directly available in the document?
LlamaParse correctly extracted the directly available receipt number as text. It also returned subtotal, tax and total due as $85.00, $5.10 and $90.10, respectively—the same amounts printed on the receipt.
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.
Plainly-labelled scalar fieldPassEvidence
We uploaded a one-page service receipt to the LlamaCloud Extract web app and supplied a schema requesting the receipt number, subtotal, tax and total due as required text fields.
{ "type": "object", "properties": { "receipt_number": { "type": "string", "description": "The receipt's identifying number, labelled 'RECEIPT NO'" }, "subtotal": { "type": "string", "description": "The subtotal amount before tax" }, "tax": { "type": "string", "description": "The tax amount" }, "total_due": { "type": "string", "description": "The total amount due" } }, "required": ["receipt_number", "subtotal", "tax", "total_due"] }
{"receipt_number": "RHS-70234", "subtotal": "$85.00", "tax": "$5.10", "total_due": "$90.10"}
JSON output: the four extracted values, returned as text.
Copied from Output file (JSON), lines 9–14
Open the JSON file ↗| ✓ | Expected: The receipt number, returned with the correct value and data type.Found: The receipt number was returned as text without label text, with a page-1 citation pointing to the number. |
Extract is LlamaParse’s feature for returning named fields, and the receipt and required schema were both supplied. It returned the printed receipt number in the required text type without its label.
Tax confidence warning. The tax field was highlighted in amber at confidence 0.8956, below the 90% threshold.
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 | Field Extraction → | |
| Scenario | The value is directly available → | |
| 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.