<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI hallucinations on Kuldeep Pisda</title><link>https://kdpisda.in/tag/ai-hallucinations/</link><description>Recent content in AI hallucinations on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 04 Oct 2025 12:44:21 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/ai-hallucinations/index.xml" rel="self" type="application/rss+xml"/><item><title>Retrieval Augmented Generation The Secret Sauce For Smarter AI</title><link>https://kdpisda.in/retrieval-augmented-generation-the-secret-sauce-for-smarter-ai/</link><pubDate>Sat, 04 Oct 2025 12:44:21 +0530</pubDate><guid>https://kdpisda.in/retrieval-augmented-generation-the-secret-sauce-for-smarter-ai/</guid><description>&lt;p&gt;Have you ever asked a chatbot a simple question and gotten a beautifully confident, yet completely wrong answer? I&amp;rsquo;ve been there. A while back, my team was building an internal tool to help our developers navigate our ever changing API documentation. The base Large Language Model was a wizard at explaining general coding concepts. But when we asked about a specific, recently updated endpoint, it hallucinated parameters that just didn&amp;rsquo;t exist.&lt;/p&gt;</description></item></channel></rss>