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

Can LlamaParse repair a record by adding one member and removing one?

LlamaParse did not let the user add or remove a member of an extracted set. The saved result stayed at three line items: Site fencing remained, and Concrete mixer was absent after the edit attempts.

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.

Add one member and remove oneFailEvidence
What we sent

After extraction, in the Extract Results view, we tried to remove the Site fencing row and add a Concrete mixer row. We looked for row controls, double-clicked a cell, typed, pressed Delete and Backspace, and right-clicked the row.

Input 1Document (PDF)
Input PDF: two-page plant-hire invoice with three line items
Open the PDF ↗
Input 2File (JSON)
Input schema: invoice line items with descriptions, quantities, unit prices and amounts
JSON
{
  "type": "object",
  "properties": {
    "line_items": {
      "type": "array",
      "description": "Every line item in the invoice table",
      "items": {
        "type": "object",
        "properties": {
          "description": {
            "type": "string",
            "description": "The description of the line item"
          },
          "quantity": {
            "type": "string",
            "description": "The quantity of the line item"
          },
          "unit_price": {
            "type": "string",
            "description": "The unit price of the line item"
          },
          "amount": {
            "type": "string",
            "description": "The amount of the line item"
          }
        }
      }
    }
  },
  "required": ["line_items"]
}
Open the JSON file ↗
What the tool returned

Copied from Output file (JSON), lines 1–30

JSON
{
  "file_input": "9b92246a-9a46-4465-aac7-181b782ac046",
  "id": "ext-j47fu0drvr2g7neyt2x5gd8yvgw6",
  "project_id": "205fc038-050f-4b9d-9896-b404e84e1434",
  "configuration_id": null,
  "configuration": null,
  "status": "COMPLETED",
  "error_message": null,
  "extract_result": {
    "line_items": [
      {
        "description": "Telehandler, 4-tonne, weekly hire",
        "quantity": "1",
        "unit_price": "£850.00",
        "amount": "£850.00"
      },
      {
        "description": "Generator, 20kVA, weekly hire",
        "quantity": "2",
        "unit_price": "£210.00",
        "amount": "£420.00"
      },
      {
        "description": "Site fencing, per 10m panel, weekly",
        "quantity": "8",
        "unit_price": "£24.00",
        "amount": "£192.00"
      }
    ]
  },

Copied from Output file (JSON), lines 316–319

JSON
  "created_at": "2026-10-28T10:32:49.939180Z",
  "updated_at": "2026-10-28T10:32:58.838635Z",
  "document_input_value": "9b92246a-9a46-4465-aac7-181b782ac046"
}

Stored output: unchanged after edit attempts; last updated 8.9 seconds after extraction was created

Open the JSON file ↗
Expected vs. Found
✗Expected: The added member is saved, the removed member is absent, and every other member stays unchanged.Found: The saved set retained all three original line items: Site fencing remained, Concrete mixer was absent, and the other entries were unchanged.
Supporting proof
Proof 1Screenshot
Screenshot before editing: three extracted line items without add or delete controls
Open original ↗
Proof 2Screenshot
Right-click screenshot: no menu appears over the Site fencing row
Open original ↗
Proof 3Screenshot
After-attempt screenshot: Site fencing remains unchanged, with description text selected
Open original ↗
Why this result

Adding and removing members was attempted on a successfully extracted set. The Free plan’s Extract review screen offered no way to do either, and the saved set stayed unchanged. This is an editing capability failure, not an extraction failure.

Also observed in this test case

Cell editing unavailable. Double-clicking the Site fencing description selected its text; it did not open a cell editor.

Tested by Rugved Nichite · evidence dated 28 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 invoice's three line items had to be extracted first with the supplied schema for descriptions, quantities, unit prices and amounts, providing a set to attempt to edit on the review screen.
Tested
28 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
CapabilityReview and Correction →
ScenarioRepair a record →
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
16 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/repair-a-record · 0 pass · 1 fail · coverage 1/1 · graded 2026-11-06

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 · 78 KB
Input 2 · File (JSON) ↗application/json · 1 KB
Output file (JSON) ↗text/plain; charset=utf-8 · 10 KB
Proof 1 · Screenshot ↗image/png · 120 KB
Proof 2 · Screenshot ↗image/png · 122 KB
Proof 3 · Screenshot ↗image/png · 122 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input 1 · Document (PDF)fdcf03ac5ee53b083da58166f17fd41e7c72de79a9f3a3f6b67daa1360ddbca9
Input 2 · File (JSON)27cb61587f29a8ad345374a88f172ec01e1d651b517832ead94392435847e360
Output file (JSON)ad78877c8fb15f49868959f825654a0dc82db91451e5af7c74eab6f1a6837794
Proof 1 · Screenshotd9cbd277adf44765c92c67f89c6bb646fa63dec9bf8bed2f773e4d9f39a795f0
Proof 2 · Screenshotb240a2846a9520822943cd3536db8350321b869b175cb04210216d620542e735
Proof 3 · Screenshot32f63b2d7f54fec8279f08c38c055549ef008ad2660db33da6ea76f6f5a55ad3