Can Dify handle a simple, clearly formatted table?
Dify passes this simple table lookup scenario. The chat answer returned £487 (excluding VAT), and the supporting passage showed that value in the Extended row under Out-of-hours callout; the retrieval output showed the same table passage.
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.
Table value asked by its row and column labelsPassEvidence
Input 1: “What is the out-of-hours callout charge on an Extended cover contract?”
Input 2: “What is the out-of-hours callout charge on an Extended cover contract?”
Response 1 answers Input 1.
Response 2, the final response, answers Input 2.
£487 (excluding VAT).
Transcript: both calls, answer, and supporting passage
Copied from Captured file (text), line 204 · an excerpt
Open the whole text file ↗Every message the tool sent, in order (2)
- Response to input 1
12. Callout and attendance charges All figures in pounds sterling, excluding VAT. Cover level Weekday callout Out-of-hours callout Offshore day rate Standard 216 352 1,140 Extended 284 487 1,265 Critical 331 615 1,408
- Final response
The final response, printed above.
Source excerpt · partial file · response 1
"records": [ { "segment": { "id": "6cbc7e60-824f-4f1a-912f-4378f4ecebf2", "position": 20, "document_id": "0eeae560-0e74-44e9-aaee-2cc6b599dee8", "content": "Where an engineer attends on two consecutive days, the second day is\r\ncharged at the day rate rather than as a second callout.\r\n12. Callout and attendance charges\r\nAll figures in pounds sterling, excluding VAT.\r\nCover level Weekday callout Out-of-hours callout Offshore day rate\r\nStandard 216 352 1,140\r\nExtended 284 487 1,265\r\nCritical 331 615 1,408\r\nOut-of-hours means any call answered outside 08:00 to 18:00, Monday to Friday, and any call answered on a statutory non-working\r\nday.", "sign_content": null, "answer": null, "word_count": 485, "tokens": 124, "keywords": [], "index_node_id": "624d063b-9d1e-43c4-bb66-819b4e92277a", "index_node_hash": "e4a353565886ce2a16a19c5b3aee50cd18fc89db5b019768a0fc9c0407925965", "hit_count": 0, "enabled": true, "disabled_at": null, "disabled_by": null, "status": "completed", "created_by": "f1034bbd-04df-4592-ba22-56dac49ae8ad", "created_at": 1789752844, "indexing_at": 1789752846, "completed_at": 1789752852, "error": null, "stopped_at": null, "document": { "id": "0eeae560-0e74-44e9-aaee-2cc6b599dee8", "data_source_type": "upload_file", "name": "A01_field_service_policy_and_charges_uk.pdf", "doc_type": null, "doc_metadata": { "region": "uk" } } }, "child_chunks": [], "score": 0.638875, "tsne_position": null, "files": [], "summary": null },
Copied from Captured file (text), lines 14–54 · an excerpt
Source excerpt · partial file · response 2
"answer": "£487 (excluding VAT).",
Copied from Captured file (text), line 204 · an excerpt
| ✓ | Expected: The value matched to its row and column, not a neighbouring row's value.Found: The chat answer gave £487 (excluding VAT), which matches the Extended row under Out-of-hours callout; the neighbouring values were not returned. |
It is a pass because the answer is the correct row-and-column value, not a neighbouring row's value, and the same table passage supports that match.
Shared passage. Both calls used the same top passage, so the answer came from the same retrieved table passage.
Usage details. The chat response reported 521 prompt tokens, 189 completion tokens, $0.0025413 and 6.51 seconds of latency, with no model name.
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 | Managed RAG → | 15 scenarios · 9 tools |
| Capability | Data Ingestion → | |
| Scenario | A simple, clearly formatted table → | |
| Tool | Dify → |
Global scenario definition → · Global capability definition → · Dify 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.