<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: sreevalli</title>
    <description>The latest articles on DEV Community by sreevalli (@sreevalli_335df1977399966).</description>
    <link>https://dev.to/sreevalli_335df1977399966</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4155546%2Fc4d98a9a-dbdc-4bcd-b1c7-2b711fd8cf9e.png</url>
      <title>DEV Community: sreevalli</title>
      <link>https://dev.to/sreevalli_335df1977399966</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sreevalli_335df1977399966"/>
    <language>en</language>
    <item>
      <title>GraphProbe AI: Building an Agentic GraphRAG System with TigerGraph</title>
      <dc:creator>sreevalli</dc:creator>
      <pubDate>Thu, 01 Oct 2026 17:55:56 +0000</pubDate>
      <link>https://dev.to/sreevalli_335df1977399966/graphprobe-ai-building-an-agentic-graphrag-system-with-tigergraph-an2</link>
      <guid>https://dev.to/sreevalli_335df1977399966/graphprobe-ai-building-an-agentic-graphrag-system-with-tigergraph-an2</guid>
      <description>&lt;h1&gt;
  
  
  GraphProbe AI: Building an Agentic GraphRAG System with TigerGraph
&lt;/h1&gt;

&lt;p&gt;Modern RAG systems are good at finding relevant pieces of information. But when a question requires connecting multiple entities, following relationships, checking evidence, and deciding what information is still missing, simple retrieval can fall short.&lt;/p&gt;

&lt;p&gt;That is the problem we explored with &lt;strong&gt;GraphProbe AI&lt;/strong&gt;.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Investigate. Connect. Verify.&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;GraphProbe AI is an Agentic GraphRAG system designed to investigate questions by combining graph relationships, retrieval, evidence evaluation, and multi-step reasoning.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Problem
&lt;/h2&gt;

&lt;p&gt;A conventional retrieval pipeline generally follows a straightforward pattern:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Question → Retrieve Documents → Generate Answer&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;This works well when the answer exists directly inside a relevant document.&lt;/p&gt;

&lt;p&gt;But consider questions such as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Which entities are connected through multiple relationships?&lt;/li&gt;
&lt;li&gt;What relationships connect several companies?&lt;/li&gt;
&lt;li&gt;What evidence supports those relationships?&lt;/li&gt;
&lt;li&gt;Which additional information is needed before an answer can be verified?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These questions require more than finding similar text.&lt;/p&gt;

&lt;p&gt;The system needs to identify entities, understand relationships, traverse a graph, retrieve supporting information, evaluate the evidence, and potentially perform another retrieval step.&lt;/p&gt;

&lt;p&gt;That is where GraphProbe AI focuses.&lt;/p&gt;

&lt;h2&gt;
  
  
  Our Approach
&lt;/h2&gt;

&lt;p&gt;GraphProbe AI combines three retrieval approaches:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;RAG&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Retrieves relevant textual information.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;GraphRAG&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Uses graph entities and relationships to provide structural context.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Agentic GraphRAG&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Allows an orchestrator to decide what to do next based on the original question, discovered entities, previous evidence, and remaining information gaps.&lt;/p&gt;

&lt;p&gt;The resulting workflow is:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Question → Entity Linking → Graph Traversal → Similarity Search → Evidence Evaluation → Verification → Answer&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The important part is that this is not simply a fixed sequence.&lt;/p&gt;

&lt;p&gt;The investigation can adapt depending on what the system discovers.&lt;/p&gt;

&lt;h2&gt;
  
  
  Agentic Investigation
&lt;/h2&gt;

&lt;p&gt;The core idea is an orchestrator that coordinates specialized investigation steps.&lt;/p&gt;

&lt;p&gt;Depending on the question and available evidence, the system can use capabilities such as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Entity linking&lt;/li&gt;
&lt;li&gt;Graph traversal&lt;/li&gt;
&lt;li&gt;Similarity search&lt;/li&gt;
&lt;li&gt;Document retrieval&lt;/li&gt;
&lt;li&gt;Evidence aggregation&lt;/li&gt;
&lt;li&gt;Multi-hop reasoning&lt;/li&gt;
&lt;li&gt;Evidence evaluation&lt;/li&gt;
&lt;li&gt;Verification&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For example, an investigation might follow:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Entity Linking → Graph Traversal → Answer&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;while another question may require:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Similarity Search → Entity Identification → Graph Traversal → Supporting Documents → Evidence Evaluation → Answer&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;This allows the investigation strategy to change according to the information available.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why TigerGraph?
&lt;/h2&gt;

&lt;p&gt;Relationships are central to the problems GraphProbe AI investigates.&lt;/p&gt;

&lt;p&gt;A graph makes it possible to represent entities and their connections explicitly rather than treating every piece of information as isolated text.&lt;/p&gt;

&lt;p&gt;TigerGraph provides the graph foundation used by our system to explore these relationships and support multi-hop investigation.&lt;/p&gt;

&lt;p&gt;Instead of only asking:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Which text looks similar to this question?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;we can also ask:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Which entities are connected, how are they connected, and what evidence supports those connections?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This combination is especially useful for relationship-heavy questions.&lt;/p&gt;

&lt;h2&gt;
  
  
  Evidence Matters
&lt;/h2&gt;

&lt;p&gt;Generating an answer is only one part of an investigation.&lt;/p&gt;

&lt;p&gt;GraphProbe AI also tracks evidence used during the investigation.&lt;/p&gt;

&lt;p&gt;The system records information such as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Retrieved evidence&lt;/li&gt;
&lt;li&gt;Connected entities&lt;/li&gt;
&lt;li&gt;Graph traversal results&lt;/li&gt;
&lt;li&gt;Retrieval operations&lt;/li&gt;
&lt;li&gt;Evidence evaluation&lt;/li&gt;
&lt;li&gt;Verification steps&lt;/li&gt;
&lt;li&gt;Agentic trace&lt;/li&gt;
&lt;li&gt;Tokens used&lt;/li&gt;
&lt;li&gt;Investigation latency&lt;/li&gt;
&lt;li&gt;Stopping reason&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This creates an investigation trace rather than only returning a final paragraph.&lt;/p&gt;

&lt;h2&gt;
  
  
  Agentic Trace
&lt;/h2&gt;

&lt;p&gt;One of the key outputs of GraphProbe AI is the agentic trace.&lt;/p&gt;

&lt;p&gt;A simplified investigation can look like:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;QUESTION
   ↓
ENTITY LINKING
   ↓
GRAPH TRAVERSAL
   ↓
VECTOR SEARCH
   ↓
EVALUATE EVIDENCE
   ↓
VERIFY
   ↓
FINAL ANSWER
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Each step records what the system attempted and what information was obtained.&lt;/p&gt;

&lt;p&gt;This makes the reasoning process easier to inspect and helps identify whether an answer is supported by the available evidence.&lt;/p&gt;

&lt;h2&gt;
  
  
  Knowing When to Stop
&lt;/h2&gt;

&lt;p&gt;An investigation should not continue indefinitely.&lt;/p&gt;

&lt;p&gt;GraphProbe AI therefore includes evidence evaluation and verification as part of the workflow.&lt;/p&gt;

&lt;p&gt;The system can determine whether the available evidence is sufficient for the current investigation and record why the process stopped.&lt;/p&gt;

&lt;p&gt;This gives the final result additional context:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What did we find?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How did we find it?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What evidence supports it?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why did the investigation stop?&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Comparing Retrieval Strategies
&lt;/h2&gt;

&lt;p&gt;GraphProbe AI also provides a comparison between:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Pipeline&lt;/th&gt;
&lt;th&gt;Approach&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;RAG&lt;/td&gt;
&lt;td&gt;Document-focused retrieval&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;GraphRAG&lt;/td&gt;
&lt;td&gt;Graph + retrieval&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Agentic GraphRAG&lt;/td&gt;
&lt;td&gt;Adaptive multi-step investigation&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The comparison helps us examine differences in retrieval behavior, evidence usage, token consumption, latency, and investigation traces.&lt;/p&gt;

&lt;p&gt;The benchmark results are generated from actual system execution rather than manually entered values.&lt;/p&gt;

&lt;h2&gt;
  
  
  Technology Stack
&lt;/h2&gt;

&lt;p&gt;The project uses:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Python&lt;/strong&gt; for the backend and investigation logic&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;FastAPI&lt;/strong&gt; for the API layer&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;TigerGraph&lt;/strong&gt; for graph-based investigation&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;GraphRAG&lt;/strong&gt; for combining graph and retrieval context&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Groq&lt;/strong&gt; for language-model generation&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Vercel&lt;/strong&gt; for the frontend&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Render&lt;/strong&gt; for backend deployment&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The architecture is designed around a clear separation between the investigation engine, graph layer, retrieval capabilities, and user interface.&lt;/p&gt;

&lt;h2&gt;
  
  
  What We Built
&lt;/h2&gt;

&lt;p&gt;The final application provides an investigation workspace where a user can submit a question and inspect:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The generated answer&lt;/li&gt;
&lt;li&gt;Connected entities&lt;/li&gt;
&lt;li&gt;Supporting evidence&lt;/li&gt;
&lt;li&gt;Agentic investigation trace&lt;/li&gt;
&lt;li&gt;Tokens used&lt;/li&gt;
&lt;li&gt;Latency&lt;/li&gt;
&lt;li&gt;Confidence information&lt;/li&gt;
&lt;li&gt;Investigation ID&lt;/li&gt;
&lt;li&gt;Stopping reason&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;There are also dedicated views for comparing retrieval approaches and examining benchmark metrics.&lt;/p&gt;

&lt;h2&gt;
  
  
  Evaluation
&lt;/h2&gt;

&lt;p&gt;For the hackathon evaluation, GraphProbe AI was tested against the provided evaluation questions.&lt;/p&gt;

&lt;p&gt;The system produces raw outputs containing:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Answers&lt;/li&gt;
&lt;li&gt;Tokens used&lt;/li&gt;
&lt;li&gt;Agentic traces&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;We also evaluate the behavior of the different retrieval pipelines using runtime-generated results.&lt;/p&gt;

&lt;p&gt;We intentionally avoid presenting manually fabricated accuracy or performance numbers. The goal is for every reported result to correspond to an actual system execution.&lt;/p&gt;

&lt;h2&gt;
  
  
  What We Learned
&lt;/h2&gt;

&lt;p&gt;Building GraphProbe AI highlighted an important difference between traditional retrieval and agentic retrieval.&lt;/p&gt;

&lt;p&gt;A useful investigation is not necessarily about retrieving more information.&lt;/p&gt;

&lt;p&gt;It is about retrieving the &lt;strong&gt;right information&lt;/strong&gt;, understanding relationships between entities, evaluating evidence, and deciding what to investigate next.&lt;/p&gt;

&lt;p&gt;Graph-based context can provide structure that pure text retrieval does not naturally expose, while an agentic layer can adapt the investigation strategy instead of following a single fixed pipeline.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's Next
&lt;/h2&gt;

&lt;p&gt;There are several directions we would like to explore:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;More sophisticated entity resolution&lt;/li&gt;
&lt;li&gt;Improved multi-hop planning&lt;/li&gt;
&lt;li&gt;Stronger evidence ranking&lt;/li&gt;
&lt;li&gt;More efficient retrieval strategies&lt;/li&gt;
&lt;li&gt;Larger graph datasets&lt;/li&gt;
&lt;li&gt;Better evaluation of agentic stopping decisions&lt;/li&gt;
&lt;li&gt;More detailed investigation analytics&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;GraphProbe AI is our exploration of what happens when GraphRAG becomes an adaptive investigation process rather than a single retrieval step.&lt;/p&gt;

&lt;p&gt;The core idea is simple:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Investigate. Connect. Verify.&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;By combining TigerGraph, retrieval, specialized investigation capabilities, evidence evaluation, and an orchestrator, GraphProbe AI turns complex questions into traceable multi-step investigations.&lt;/p&gt;

&lt;p&gt;The result is not just an answer.&lt;/p&gt;

&lt;p&gt;It is an answer accompanied by the path, evidence, and reasoning process used to reach it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Project
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;GraphProbe AI&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Repository:&lt;/strong&gt;&lt;br&gt;
&lt;a href="https://github.com/Sreevalli20/agentic-tiger" rel="noopener noreferrer"&gt;https://github.com/Sreevalli20/agentic-tiger&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Live Application:&lt;/strong&gt;&lt;br&gt;
&lt;a href="https://frontend-gamma-ecru-m8dndislo7.vercel.app" rel="noopener noreferrer"&gt;https://frontend-gamma-ecru-m8dndislo7.vercel.app&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Backend:&lt;/strong&gt;&lt;br&gt;
&lt;a href="https://graphprobe-ai-backend.onrender.com" rel="noopener noreferrer"&gt;https://graphprobe-ai-backend.onrender.com&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>graphrag</category>
      <category>tigergraph</category>
      <category>python</category>
    </item>
  </channel>
</rss>
