Can Vectara handle retrieved sources that disagree with each other?
Vectara said it could not determine the warranty period on a new Tolvan A3 because its search results conflict, and named neither 24 nor 36 months as the fact. Both conflicting warranty documents were among the passages it retrieved, at ranks 1 and 2.
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.
Two documents give different values for the same factPassEvidence
“What is the warranty period on a new Tolvan A3?”
I do not have enough information to accurately determine the warranty period on a new Tolvan A3, as the search results provide conflicting information.
Text record: the question, Vectara's answer and the retrieved passages with their scores
Copied from Captured file (text), line 8
Open the text file ↗| ✓ | Expected: The answer conveys that the sources differ, rather than presenting one value as the fact.Found: Both documents were retrieved, 36 months at rank 1 and 24 months at rank 2 with equal scores; the answer says the results conflict and states neither value as fact. |
It is a Pass: the case requires the answer to convey that the sources differ rather than present one value as the fact. Both documents were retrieved, nothing in the passages says which one supersedes, and the answer says they conflict instead of choosing one.
Moderate consistency score on a decline. Vectara's own factual consistency score for this answer was 0.336. On an answer that declines to pick between conflicting sources, this reflects passages that support no single value, not an ungrounded claim.
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 | Grounded Generation → | |
| Scenario | The retrieved sources disagree with each other → | |
| 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.