Something more famous has the same name
A query targets a less famous entity that shares its name with a more famous one.
What this scenario means
This tests whether retrieval can separate the intended entity from a better-known namesake. It is hard because the stronger association can pull results toward the wrong target while still looking plausible. A good system finds evidence for the intended entity, keeps the namesake from dominating, and does not act certain about the wrong match.
What we evaluate
- Whether the system recognises the intended entity rather than defaulting to the more famous namesake.
- Whether it avoids confidently returning results about the wrong same-named entity.
- Whether it keeps retrieval focused on the less famous target when the namesake is the stronger public association.
Capabilities this scenario exercises
A scenario may exercise one or more capabilities.
Web Retrieval
When the web holds material that supports the answer, does it come back? Judged against the WEB, not against what the tool retrieved: if the answer was out there and search missed it, that is a retrieval failure. The developer does not know which URL holds the answer -- the product has to find it, which is the whole category.
Benchmarks that use this scenario
A scenario has global identity and may be reused across benchmarks.
Web Search for AI
Which web search or answer API finds the live-web material that actually supports an answer, keeps up when that material changes, and -- where it writes the answer itself -- says only what its own sources support?