Look It Up: Analysing Internal Web Search Capabilities of Modern LLMs

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2511.18931v2 Announce Type: replace-cross Abstract: Modern large language models increasingly integrate internal web-based retrieval to provide real-time answers, yet it remains unclear how effectively these systems identify information need, trigger retrieval, and use retrieved evidence. To understand these parameters better, we evaluate the necessity and effectiveness of internal web search through an external lens in closed-source LLMs, without access to model parameters or internal configuration. Our evaluation method comprises a static split of 783 temporally anchored factual queries answerable from pre-cutoff knowledge, designed to test whether retrieval is invoked based on factual uncertainty, and a dynamic split of 288 post-cutoff queries that require up-to-date information, designed to evaluate retrieval effectiveness under unavoidable information need. We experiment across four models across two model families and scales. Across models, enabling retrieval yields substantial accuracy gains on the static split, but systematically degrades confidence calibration. On the dynamic split, models frequently invoke retrieval yet remain below 70 percent accuracy, with failures dominated by query formulation and source selection errors rather than integration of retrieved content. While retrieval is inexpensive to invoke and can be selectively beneficial, repeated retrieval attempts rarely recover from early failures, and confidence becomes inflated once retrieval is available. Overall, internal web-based retrieval functions effectively as a low-latency verification …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2511.18931
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.