Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Introducing SelfGraph. The open source framework for building agent graphs. Turn unstructured text into a graph your agents can query. Every fact keeps its source. Same framework. Any graph store. Link in comments.

28,769 görüntüleme • 4 gün önce •via X (Twitter)

29 Yorum

HydraDB profil fotoğrafı
HydraDB4 gün önce

Repo Link :

aditya. profil fotoğrafı
aditya.3 gün önce

AYOOOO FINALLYYYY

abhinav profil fotoğrafı
abhinav4 gün önce

🔥 less go

Soham Ratnaparkhi profil fotoğrafı
Soham Ratnaparkhi4 gün önce

Easiest way to graph anything Lesss gooo

Vyom profil fotoğrafı
Vyom4 gün önce

Lessgoooo; excited for this !!!

Aditya Shrivastava profil fotoğrafı
Aditya Shrivastava3 gün önce

Graph it out!

Eshwar Prasad Yaddanapudi profil fotoğrafı
Eshwar Prasad Yaddanapudi3 gün önce

Been following @hydra_db from your launch video. This is a great direction. Congratulations!

Ani (YC F26) profil fotoğrafı
Ani (YC F26)3 gün önce

its funny to see the stars on repo at 300 in the morning and now at 48. why would someone go back to unstar it?

Jayking♟️ profil fotoğrafı
Jayking♟️4 gün önce

Love these Can I build with you guys early

Chen profil fotoğrafı
Chen4 gün önce

every fact keeping its source is such a good call. way too many agent graphs just lose all provenance.

Lane Henslee profil fotoğrafı
Lane Henslee4 gün önce

The notes file my agents pass from one run to the next is capped at 3,000 characters, so it has room for a fact but not for where the fact came from

HydraDB profil fotoğrafı
HydraDB4 gün önce

Use

Nox profil fotoğrafı
Nox4 gün önce

every fact keeping its source is the whole point tbh

Harsh profil fotoğrafı
Harsh4 gün önce

🚀🚀

Cole Whitman profil fotoğrafı
Cole Whitman3 gün önce

Turning unstructured data into reliable, traceable knowledge is a big win for AI agents.

Zo profil fotoğrafı
Zo4 gün önce

Can you query what the agent knew at the time, separately from when a fact was true? Thinking of a correction learned today that gets backdated to last week.

Yashas profil fotoğrafı
Yashas3 gün önce

@SohamR_7113 Who’s the lead at hydra? (pref cto, ceo) hmu

FutureTechTeller profil fotoğrafı
FutureTechTeller3 gün önce

Every fact keeps its source. The only feature that matters for audit-sensitive environments. I would run the same provenance checks on factory data pipelines and digital twin layers.

Vasu Pal profil fotoğrafı
Vasu Pal4 gün önce

@graphify ?

Grumpy profil fotoğrafı
Grumpy4 gün önce

traceability per node makes checking wrong answers trivial, merging conflicting claims is where these usually break

Prakalp Choubey profil fotoğrafı
Prakalp Choubey3 gün önce

graph for graphs?

HydraDB profil fotoğrafı
HydraDB3 gün önce

Graphs for “everything” that is scattered and disconnected 😉

Snazzie profil fotoğrafı
Snazzie3 gün önce

Hasnt graphs been proven to not help? atleast it hasnt helped me

HydraDB profil fotoğrafı
HydraDB3 gün önce

Well, give us a try. There's something waiting for you on the other side 😉

Smobile profil fotoğrafı
Smobile3 gün önce

keeping the source on every fact is the part that matters

Raviv Golov profil fotoğrafı
Raviv Golov4 gün önce

Every fact keeps its source" is the feature that matters. Graph RAG without provenance is just confident hallucination with extra hops. Being store-agnostic also means nobody has to migrate their graph DB just to try it.

生晓bai profil fotoğrafı
生晓bai3 gün önce

Keeping the source attached to every fact is the part most agent-memory demos conveniently skip.

Aivatar profil fotoğrafı
Aivatar3 gün önce

Turning unstructured text into queryable agent graphs with source attribution attacks the exact pain point of RAG — answers without receipts. The attribution part is what makes this usable in real work: you can check where the graph got it. How does it handle conflicting sources in the same corpus?

Gunmay Jhingran profil fotoğrafı
Gunmay Jhingran3 gün önce

Lets goo 🚀🚀

Benzer Videolar

Build better RAG by letting a team of agents extract and connect your reference materials into a knowledge graph. Our new short course, “Agentic Knowledge Graph Construction,” taught by Neo4j Innovation Lead Andreas Kollegger, shows you how. Knowledge graphs are an important way to store information accurately but they are a lot of work to build manually. In this course you’ll learn how to build a team of agents that turn data– in this case product reviews and invoices from suppliers–into structured graphs of entities and relationships for RAG. Learn how agents can automatically handle the time-consuming work of building graphs — extracting entities and relationships (e.g., Product "contains" Assembly, Part "supplied_by" Supplier, Customer review "mentions" Product), deduplicating them, fact-checking them, and committing them to a graph database — so your retrieval system can find right information to generate accurate output. For example, you can use agents to help trace customer complaints directly to specific suppliers, manufacturing processes, and product hierarchies, thus turning fragmented information into queryable business intelligence. Skills you’ll gain: - Build, store, and access knowledge graphs using the Neo4j graph database - Build multi-agent systems using Google’s Agent Development Kit (ADK) - Set up a loop of agentic workflows to propose and refine a graph schema through fact-checking - Connect agent-generated graphs of unstructured and structured data into a unified knowledge graph This course gets into the practicum of why knowledge graphs give more accurate information retrieval than vector search alone, especially for high-stakes applications where precision matters more than fuzzy similarity matching. Sign up here:

Andrew Ng

169,184 görüntüleme • 1 yıl önce