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

Does Denser AI keep a simple table's values under the right headers?

Denser AI handled this simple table lookup correctly. It returned £487 for the Extended out-of-hours cell, and the retrieved table also showed the nearby values 352, 615 and 284 without using them as the answer. The notebook capture and the call log showed the same answer.

1 of 1 test case passed

Every test case in this scenario has a result.

Pass rate100%1 of 1 gradable
Coverage1 of 1test case with a result
1PassDid everything it was expected to do.
0FailNo test case failed.
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.

Table value asked by its row and column labelsPassEvidence
What we sent

“What is the out-of-hours callout charge on an Extended cover contract?”

What the tool returned

The out-of-hours callout charge on an Extended cover contract is £487 (excluding VAT).

Show the reply as returned (Markdown)
The out-of-hours callout charge on an Extended cover contract is **£487** (excluding VAT).

API call log: the answer and ten retrieved passages

Copied from Output file (text), lines 7–13 · an excerpt

Open the whole text file ↗

Source excerpt · partial file · response 1

Text
status: 200 | passages returned: 10

--- answer (verbatim, includes Denser's own inline citation marker) ---
The out-of-hours callout charge on an Extended cover contract is **£487** (excluding VAT).[1](upload
/google_107814369447848734045/chatbots/chatbot_o9ihun9849fcf3tbhigo4/ruM2xi4mokcyDojzyRmgA.pdf
PassageID:0)

Copied from Output file (text), lines 7–12 · an excerpt

Expected vs. Found
✓Expected: The value should match the named row and column, and a neighbouring row's value should not count as a match.Found: It returned £487 for the Extended out-of-hours cell; the nearby values 352, 615 and 284 were visible in the retrieved table but were not the answer.
Supporting proof
Proof 1Screenshot
Notebook screenshot: the same answer and top passage
Open original ↗
Why this result

It had to return the value at the named row and column, not a neighbouring table value. It did: £487 matches the Extended out-of-hours cell, and the neighbouring values in the same retrieved table (352, 615 and 284) were not used as the answer.

Also observed in this test case

No ingestion API. Denser had no ingestion API on any plan, so the corpus had to be uploaded through the web app.

Tested by Vivek Tomar · evidence dated 1 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
Denser AI
Build or version
Not exposed by the hosted product
Plan or tier
Free
Surface
API
Set up before the run
The Fenwake Field Service Policy and Charges document, with its callout-charges table (rows Standard, Extended and Critical cover; columns weekday callout, out-of-hours callout and offshore day rate), was uploaded to Denser. The question named the Extended row and the out-of-hours callout column.
Citations
on
Tested
1 October 2026 · Vivek Tomar

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
BenchmarkManaged RAG →15 scenarios · 9 tools
CapabilityData Ingestion →
ScenarioA simple, clearly formatted table →
ToolDenser AI →

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 publishedManaged RAG 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/managed-rag/results/denser-ai/a-simple-clearly-formatted-table · 1 pass · 0 fail · coverage 1/1 · graded 2026-10-12

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.

Output file (text) ↗text/plain; charset=utf-8 · 16 KB
Proof 1 · Screenshot ↗image/png · 321 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Output file (text)9fcb880368d6c9c2be1cb7c4390434078594c7269b9a9b372cb694140b34f8e6
Proof 1 · Screenshot8b523567060a497119856fb7a1304434bb0b5b9f1c6df1f5ebd49823ce98e93a