Interactive Lab · How LLMs stay honest

Why does an LLM make things up, and how does giving it a search box fix that?

An LLM only knows what was baked into its weights. Ask it something it never saw, your company's refund policy, a niche recent fact, and it will answer confidently and wrongly. RAG bolts a search step in front of it: retrieve the real documents, hand them over, and make it quote the truth. Flip retrieval on and off below and watch the same question flip from fiction to fact.

🎬 Watch the 45-second explainer, then try it yourself below ↓

▶ The playground, pick a question, flip retrieval, hit Ask

Pick a question

❓Your question
→
🔎Retrieversearches KB
→
🤖LLMgenerates
→
✅Answer

🧭 Where this fits

RAG is the architecture of virtually every enterprise AI assistant shipped since 2023, customer-support bots grounded in help docs, legal/medical copilots with citations, internal-knowledge chat. The poisoned-KB failure you just triggered is the field's core operational lesson: RAG moves the failure from the model's memory to YOUR retrieval pipeline, which is why retrieval evals (see the RAG-eval lab) are a job.

The code that's actually running



  

🔮 Predict, then test

Pick "BitBootcamp's refund policy" and turn retrieval OFF, will the LLM admit it doesn't know, or invent a plausible-sounding policy? Now flip it ON. Finally, keep RAG on but flip ☠️ Poison the KB: the answer is still grounded and confident, so why is it wrong? What does that tell you about where a RAG system actually fails?

The takeaway

Your new mental model of RAG