Can Vectara retrieve the right passage when the query uses different wording?
Vectara returned the matching passage even though the question used different wording from the source. In both retrieval runs, the annual leave passage was rank 1, and the returned passages did not contain the query's alternative terms.
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.
Question asked with a term absent from the corpusPassEvidence
“How many days of paid time off do employees get each year?”
Annual leave Full-time employees accrue 26 days of annual leave in each complete leave year, which runs from 1 April to 31 March.
Text dump: both retrieval runs and the full result lists
Copied from Output file (text), lines 9–10 · an excerpt
Open the whole text file ↗Source excerpt · partial file · response 1
--- rank 1 | score=0.853053 | doc=A04_employee_handbook.docx | page=None --- Annual leave Full-time employees accrue 26 days of annual leave in each complete leave year, which runs from 1 April to 31 March.
Copied from Output file (text), lines 9–10 · an excerpt
| ✓ | Expected: The supporting passage still comes back.Found: The annual leave passage is rank 1 in both retrieval runs, and the returned passages do not use the query's alternative wording. |
The query used a term absent from the corpus, and the annual leave passage still ranked first in both retrieval runs. The returned passages do not use the query wording, so this case is a pass.
Second rank changes. The second result changes between the two runs, but the annual leave passage stays first in both.
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 · 7 tools |
| Capability | Retrieval → | |
| Scenario | The request uses different wording than the source → | |
| Tool | Vectara → |
Global scenario definition → · Global capability definition → · Vectara 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.