🏃 Keep Up
← All topics
RAG 9 items

Everything RAG

🟧 Hacker News 2w ago

NotebookLM Rebrands as Gemini Notebook

Google rebranded NotebookLM as Gemini Notebook, integrating it more tightly into the Gemini product family. The HN thread drew 153 points — mostly practitioners noting the product utility while questioning whether the rename signals deeper integration with Gemini models or is primarily a marketing move. NotebookLM/Gemini Notebook remains one of the more actively adopted RAG-adjacent products among knowledge workers.

📑 arXiv 2w ago

DeepStress: Stress-Testing Deep Search Agents

Framework for stress-testing multi-step search agents under poor-quality evidence conditions — a failure mode that is rare in standard benchmarks but catastrophic in production. DeepStress controls the frequency and severity of misleading/noisy evidence in retrieved documents and measures agent robustness, exposing brittleness invisible to standard QA metrics. Relevant for any practitioner deploying RAG-based or web-search agents in adversarial or noisy environments.

📑 arXiv 3w ago
⭐ Editor's Pick

Do You Need a Frontier Model as a Citation Verifier? Benchmarking Rubric LLMs for Deep-Research Source Attribution

As RLVR increasingly uses an LLM judge as the reward model, this paper asks: how capable must the judge be, and how biased is it? Studies this calibration question specifically for citation quality in deep-research systems — a practically important but understudied reward signal. Finds that frontier models are not always necessary as citation judges, and characterizes the bias profile of smaller rubric LLMs. Directly informs design of reward models for training web-grounded research agents.

📑 arXiv 3w ago

WebSwarm: Recursive Multi-Agent Orchestration for Deep-and-Wide Web Search

Addresses the depth-vs-breadth tradeoff that limits single-agent ReAct-style web search: one long trajectory cannot simultaneously go deep on sub-questions and cover broad coverage. WebSwarm uses recursive multi-agent orchestration where a coordinator dynamically spawns specialized sub-agents for sub-queries and synthesizes their outputs, enabling parallelism across breadth while each sub-agent can depth-search independently. Targets complex research-oriented queries where current single-agent and naive multi-agent approaches fall short.

📑 arXiv Apr 22

Automatic Ontology Construction Using LLMs as an External Layer of Memory, Verification, and Planning for Hybrid Intelligent Systems

Proposes a hybrid architecture where LLMs are augmented with an automatically constructed RDF/OWL ontology as an external memory layer, replacing or supplementing vector-based RAG with a structured knowledge graph. The pipeline performs entity recognition, relation extraction, triple generation, and SHACL/OWL validation from heterogeneous sources, enabling persistent and verifiable reasoning. The key distinction from standard RAG is that retrieved context is semantically structured and constraint-validated rather than embedding-similarity ranked.

💬 Reddit Apr 21

I built a /graphify skill for Claude Code that maps your entire codebase into a knowledge graph, 71x fewer tokens, way less hallucination (32k stars, 250k downloads)

Graphify is a Claude Code skill that builds a queryable knowledge graph of a codebase using tree-sitter ASTs across 25 languages, then writes a GRAPH_REPORT.md for Claude to read instead of raw files — reporting 71.5x token reduction per query. The tool also does semantic extraction over docs, PDFs, images, and audio (via Whisper) and detects cross-file dependency communities. 32k GitHub stars and 250k PyPI downloads suggest real adoption; the token reduction claim warrants independent benchmarking.

💬 Reddit Apr 20

Spent a weekend actually understanding and building Karpathy's "LLM Wiki" — here's what worked, what didn't

A hands-on build report on Karpathy's 'LLM Wiki' concept — pre-processing sources into a structured, interlinked markdown wiki rather than retrieving raw chunks at query time. Synthesis and cross-document reasoning questions improve noticeably versus RAG, but the approach struggles with scale, update latency, and source conflicts. Honest tradeoff analysis rather than a benchmark.