AI Demos Research — the structured-intelligence platform. Every verdict on these pages opens to the execution behind it.
Graded 16 November 2026

Can LlamaParse answer about a document fact that is not in the schema?

LlamaParse offered no place to ask about a fact printed on the receipt that the extraction schema left out. Neither the Parse result screen and its menu nor the Extract results panel has a question or chat box, and Chat cannot start until an index exists.

1 of 1 test case failed

Every test case in this scenario has a result.

Pass rate0%0 of 1 gradable
Coverage1 of 1test case with a result
0PassNo test case passed.
1FailMissed at least one thing it was expected to do; the reason and proof are with each test case below.
0Not gradableEvery result here could be graded.
0UntestedEvery test case in this scenario has a result.
The pass rate is a summary. The evidence is the test case below: what we sent, what we checked, what the tool returned, and the proof.

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.

Answer outside the schema, attributedFailEvidence
What we sent

We parsed the receipt once and looked for a question control on the result screen and its More actions menu, then ran Extract once with a two-field schema and looked again. We also tried to reach Chat through a folder and an index. No question was accepted.

Input 1Document (PDF)
Input PDF: the one-page service receipt, with the technician printed in its header row
Open the PDF ↗
Input 2File (JSON)
Extraction schema: two fields, receipt number and loyalty membership number, with no technician field
JSON
{
  "type": "object",
  "properties": {
    "receipt_number": {
      "type": "string",
      "description": "The receipt's identifying number, labelled 'RECEIPT NO'"
    },
    "loyalty_membership_number": {
      "type": "string",
      "description": "The customer's loyalty program membership number, if the document mentions one."
    }
  },
  "required": ["receipt_number", "loyalty_membership_number"]
}
Open the JSON file ↗
What the tool returned

The tool's response has no text to quote: it is what the evidence under Proofs shows.

Proof 1 · Screenshot

Proof 2 · Screenshot

Expected vs. Found
✗Expected: It keeps the two apart: it says the fact is not in the extracted data, or answers and says the answer came from the document.Found: No question could be put. The parse result's menu holds only Download, Run Extract, Diagnostics and Report issue, the Extract panel has no question box, and Chat needs an index first.
Supporting proof
Proof 1Screenshot
Screenshot: the parse result and its More actions menu, with no question item
Open original ↗
Proof 2Screenshot
Screenshot: the extraction results for both fields, with no question or chat box
Open original ↗
Proof 3Screenshot
Screenshot: the Chat screen, which cannot start without an index
Open original ↗
Proof 4Screenshot
Screenshot: creating an index from the product's sample documents, refused on the Free plan
Open original ↗
Proof 5Screenshot
Screenshot: creating a folder with the receipt, refused on the Free plan
Open original ↗
Why this result

The test needed a way to ask about the technician, a fact on the receipt but not in the schema. It is a Fail, not a blocked run: parse and extraction both succeeded on the Free plan, and the product has no place to put the question.

Also observed in this test case

Plan refusal. Creating a folder under Files and creating an index, even from the product's own sample documents, were both refused on the Free plan with a message asking for a Starter, Pro or Enterprise plan.

Technician read correctly. The parsed Markdown of the receipt includes the technician's name from its header row, so the fact asked about was read off the page correctly.

Empty field flagged. The extraction results flagged the second field, loyalty membership number, as empty and below the 90% confidence line: the product marks a field it could not fill, but only for schema fields.

Tested by Rugved Nichite · evidence dated 13 October 2026

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.

Software that produced the output
LlamaParse
Build or version
LlamaCloud web app (build v09046f5c); Extract, Agentic tier
Plan or tier
Free plan (20,000 credits)
Surface
Web app
Set up before the run
The receipt names its technician plainly, and the two-field schema (receipt number, loyalty membership number) leaves the technician out, so an answer from the document would be correct. A question about the technician had to be put to the product.
Confidence threshold
90%
Tested
13 October 2026 · Rugved Nichite

How this scenario is graded

How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.

How results are decided

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.

The rules
  • 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.

LevelNameScope
BenchmarkStructured Document Extraction →19 scenarios · 10 tools
CapabilityQuerying →
ScenarioThe answer was never in the schema →
ToolLlamaParse →

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.

from the publication record
17 November 2026First publishedStructured Document Extraction v1

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.

This matches what I see

You run the same kind of test against your own setup and get the same behaviour.

Agree →
This does not match

Yours behaves differently. Tell us what you got, with a screenshot if you have one.

Disagree →
Point out an issue

Something here is wrong — a reference value, a transcription, a grade.

Report an issue →
Request a retest

On a newer build, a larger dataset, or your own setup.

Request a retest →
We have fixed this

Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.

Vendor notice →
Filed against this evidenceNothing yet. Challenges, counter-evidence and fix notices appear here with their outcome, and stay on the page after they are resolved.
Cite this result
aidemos.com/benchmarks/structured-document-extraction/results/llamaparse/the-answer-was-never-in-the-schema · 0 pass · 1 fail · coverage 1/1 · graded 2026-11-16

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.

Input 1 · Document (PDF) ↗application/pdf · 54 KB
Input 2 · File (JSON) ↗application/json · 0 KB
Proof 1 · Screenshot ↗image/png · 166 KB
Proof 2 · Screenshot ↗image/png · 115 KB
Proof 3 · Screenshot ↗image/png · 50 KB
Proof 4 · Screenshot ↗image/png · 136 KB
Proof 5 · Screenshot ↗image/png · 70 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input 1 · Document (PDF)a96bbe1c5b22336e7b54169baf72b85e45eabf1312cd293a1821017b52fa85f7
Input 2 · File (JSON)54b1f12a5fd8e4f077ae83dec6873a68a69f849b6eeaac6c834adab355f3a3c8
Proof 1 · Screenshota173760dab31dc8ffbe2dce93e07024f1f1022869692542a6b098a24bda0a178
Proof 2 · Screenshotb8316182ab9d7e06453b46b0266367c52132c92dd003777aa82e52519edf1176
Proof 3 · Screenshot2348e9180cf34e1ca5d3439aca6424a2c20d535d5029d7b917a50e66f1ed476e
Proof 4 · Screenshot63b4d0045771dcce6aa60683be45bcc89fce3cdc15958a13406f296fc337641d
Proof 5 · Screenshotf1e79d95da4d2b237ecf4ceb89c44ccd2dbf4a291caeb297d5837bcaaaa45eed