<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/c1822582396d4704a1a54901f8995bf0&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/c1822582396d4704a1a54901f8995bf0-4ef328429201fefb.gif</thumbnail_url><duration>248.531</duration><title>Building Event-Driven Knowledge Graph Workflows</title><description>This Loom demonstrates an event-driven workflow system that builds a knowledge graph from incoming Telegram links and prevents duplicate ingestions. When a link is sent, it is first saved to the database, and if the message URL already exists it reports that it is already in the knowledge graph. It then triggers subsequent workflows to extract content and run a GraphBuilder, producing a report with 52 nodes and 38 edges for the example article. The speaker notes the project is about 70% complete and is planning to build an agentic system on top of the knowledge graph.</description></oembed>