outworked.lol
#8 in Engineering#36 overallAll of @verbove’s filed tweets →
36

Here’s your explanation rewritten into a tighter GraphRAG pipeline: 1. Split the conversation or documents into text units such as messages or chunks. 2. Use an LLM to extract entities from each text unit, including type and usually a short description. 3. Use the LLM to extract relationships between entity pairs in that same text unit. 4. Save the supporting source text / text-unit ID as provenance for each extracted fact. 5. Convert the extracted facts into triples: subject, predicate, object. 6. Merge duplicates and normalize names into canonical entities like one node for Cypher instead of many slightly different spellings. 7. Build a nodes table for entities and an edges table for relationships between node IDs. 8. Store that graph so it can later be traversed, filtered, embedded, or queried with something like Cypher

Teaches 8-step GraphRAG pipeline implementation methodology

🔖 020👁 564mo ago
107107 of 1000 · 1k–10k followersReach3×0 bookmarks + 2×0 quotes + 1.5×0 replies + 2 likes = 2, against a cap of 1.5k for this league90/600Per viewer0.2% of 56 viewers did something; 5% is full marks16/400Bookmarks weigh most because people save what they intend to reuse. Every part saturates.hide
@verbove Today marks the first day of my 100 day challenge: I'm breaking down one first-principle AI concept daily in under 4 slides. There's endless jargon flying around, and most people don't understand the fundamentals. 2000 word articles explaining nothing. Time for a change. https://t.co/X6PSi5Ydwl
Bookmarks0
Likes2
Replies0
Quotes0
Views56
League1k–10k followers

Open on X · Boost ♥ · Permanent page

Filed under Engineering by the model because: Teaches 8-step GraphRAG pipeline implementation methodology. The rules.

Martijn Verbove on Engineering · Outsmart