<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Knowledge Graphs on Nalar</title>
    <link>https://nalar.dev/tags/knowledge-graphs/</link>
    <description>Recent content in Knowledge Graphs on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 08 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/knowledge-graphs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Retrieve Multi-Hop Evidence with Graph RAG</title>
      <link>https://nalar.dev/retrieve-multi-hop-evidence-with-graph-rag/</link>
      <pubDate>Tue, 08 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/retrieve-multi-hop-evidence-with-graph-rag/</guid>
      <description>&lt;p&gt;Retrieval-augmented generation (RAG) usually starts with a simple idea: find text chunks similar to a question, place the most relevant chunks in the model&amp;rsquo;s context, and ask the model to answer from that evidence. This works well when the answer is stated in one passage or in several passages that are independently easy to retrieve.&lt;/p&gt;&#xA;&lt;p&gt;Some questions are harder because the useful evidence is connected by &lt;strong&gt;relationships&lt;/strong&gt;, not just by similar wording. A developer may need to answer, &amp;ldquo;Which service depends on the library maintained by the team that owns the payment API?&amp;rdquo; No single chunk has to contain all of those words. The answer may require following several links across services, libraries, teams, and APIs.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
