正在加载视频...

视频加载失败

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 次观看 • 4 天前 •via X (Twitter)

29 条评论

HydraDB 的头像
HydraDB4 天前

Repo Link :

aditya. 的头像
aditya.3 天前

AYOOOO FINALLYYYY

abhinav 的头像
abhinav4 天前

🔥 less go

Soham Ratnaparkhi 的头像
Soham Ratnaparkhi4 天前

Easiest way to graph anything Lesss gooo

Vyom 的头像
Vyom4 天前

Lessgoooo; excited for this !!!

Aditya Shrivastava 的头像
Aditya Shrivastava3 天前

Graph it out!

Eshwar Prasad Yaddanapudi 的头像
Eshwar Prasad Yaddanapudi3 天前

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

Ani (YC F26) 的头像
Ani (YC F26)3 天前

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♟️ 的头像
Jayking♟️4 天前

Love these Can I build with you guys early

Chen 的头像
Chen4 天前

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

Lane Henslee 的头像
Lane Henslee4 天前

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 的头像
HydraDB4 天前

Use

Nox 的头像
Nox4 天前

every fact keeping its source is the whole point tbh

Harsh 的头像
Harsh4 天前

🚀🚀

Cole Whitman 的头像
Cole Whitman3 天前

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

Zo 的头像
Zo4 天前

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 的头像
Yashas3 天前

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

FutureTechTeller 的头像
FutureTechTeller3 天前

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 的头像
Vasu Pal4 天前

@graphify ?

Grumpy 的头像
Grumpy4 天前

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

Prakalp Choubey 的头像
Prakalp Choubey3 天前

graph for graphs?

HydraDB 的头像
HydraDB3 天前

Graphs for “everything” that is scattered and disconnected 😉

Snazzie 的头像
Snazzie3 天前

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

HydraDB 的头像
HydraDB3 天前

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

Smobile 的头像
Smobile3 天前

keeping the source on every fact is the part that matters

Raviv Golov 的头像
Raviv Golov4 天前

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 的头像
生晓bai3 天前

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

Aivatar 的头像
Aivatar3 天前

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 的头像
Gunmay Jhingran3 天前

Lets goo 🚀🚀

相关视频

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 次观看 • 1 年前