Ground your LLMs with structured knowledge — and leave with a full pipeline, from data ingestion to agentic retrieval, that you know how to keep production-ready.
First cohort launches September 25, 2026. We keep the group small — 20 seats. A short call is all it takes to find out if this is right for you.
No commitment required. If the course isn't the right fit, we'll tell you — and suggest what to do instead.
Build knowledge graph pipelines from structured and unstructured data using open-source LLMs
Design and query graphs in both Labeled Property Graph (LPG) and Resource Description Framework (RDF)
Implement GraphRAG pipelines and agentic retrieval systems grounded in graph structure
Apply Graph Neural Networks (GNNs) to real use cases like fraud detection and recommendations
Deploy, monitor, and maintain knowledge graph systems in production environments
Each week is a live session — part lecture, part hands-on lab, part honest conversation about what actually works in production and what doesn't. The goal isn't to cover everything. It's to make sure you leave with something you can build on.
Everything you need to understand graphs from the ground up: graph theory, knowledge graph fundamentals, the main modeling paradigms, and the technology landscape. More importantly — how graphs, LLMs, and machine learning actually interact, and why that combination is more powerful than any of them alone.
The decisions you make here will haunt you — or reward you — for the rest of the project. Labeled Property Graph (LPG) vs Resource Description Framework (RDF), when to reach for Web Ontology Language (OWL), how to write validation rules with SHACL (Shapes Constraint Language). Get these foundations right and everything else becomes easier.
We run the same real-world dataset through two different paradigms — same questions, different approaches. You'll see exactly how LPG and RDF tackle the same problem, where each shines and where it struggles. Then we explore what your graph can already tell you on its own: centrality, community detection, pathfinding — fast, interpretable, and underrated.
Where graphs actually come from. We build an end-to-end ingestion pipeline — structured data, unstructured text, extraction with open-source LLMs. Then the real question: do you reuse an existing ontology or design your own? We'll work through both paths and understand when each is the right call.
Retrieval-augmented generation is table stakes. Graph-based retrieval is the edge. We build agents that traverse your graph to answer questions no vector store can touch — multi-hop reasoning, context assembly, grounded generation. And yes, we talk honestly about where it still fails.
Stateless agents forget everything after each conversation. Agentic memory changes that — giving your systems the ability to accumulate, update, and reason over knowledge across sessions. We explore memory architectures for knowledge graphs, work hands-on with Cognee, and discuss when persistent memory is a feature versus a liability.
This is where graph embeddings get the depth they deserve. We move from theory to practice using PyTorch Geometric — building models that learn from graph structure, not just node features — applied to real use cases like recommendation systems and fraud detection. You'll leave knowing not just how Graph Neural Networks (GNNs) work, but when to reach for them and when not to.
Building the first version is the easy part. This week is about everything that happens after: monitoring graph quality over time, evaluating retrieval, orchestrating pipelines, and knowing when your system is quietly degrading. The boring stuff that makes or breaks production AI.
The hardest problem in knowledge graphs isn't technical. It's organisational. How do you get a company to think in graphs? How do you build the internal culture, the processes, and the buy-in that turn a proof of concept into a strategic asset? We close with project presentations — each participant presents an end-to-end system built across the nine weeks. Solo or in pairs, formed organically through the Discord community. The conversation most courses never have, ending with something real.
The definitive practical guide to building production-grade AI systems grounded in knowledge graphs. Covers graph modeling, LLM integration, GraphRAG pipelines, and GNN-based reasoning — with real-world code throughout.
Get the Book → Preview on ManningI've spent the last decade doing two things that don't always go together well: research and shipping. My PhD was on knowledge graphs. Since then I've built them for public sector data pipelines, medical AI systems, editorial intelligence tools — and I've watched plenty of well-designed architectures quietly fail in production because nobody talked honestly about the hard parts.
Before that, I worked as a journalist and in communications. I spent years learning how to explain complex things to people who don't have time to be confused — and that background shapes how I teach. I'm not interested in impressing you with jargon. I'm interested in making sure you actually understand what's happening under the hood.
This course is what I wish had existed when I started. Not a survey of papers, not a vendor tutorial — a structured nine weeks of building real things, making real mistakes, and understanding why the decisions you make early end up mattering so much later. I'll be in every session, not as a talking head, but as someone who's still in the trenches and genuinely enjoys the conversations that happen when a room full of engineers starts pushing on the edges of what these systems can do.
Best Paper Award — AICT 2024
Hands-on session with the audience — KGC 2025
Two tiers — Standard and Mentorship. Early bird pricing ($799 / $1,499) is available for the first 10 spots. Full price ($1,199 / $2,199) applies after.
Available to the first 10 participants. Projects are individual — work solo or pair up with another participant via Discord.
Everything in the standard tier, plus two 1:1 sessions with Giuseppe to review your project and architecture.
Only 20 seats per cohort — filled through individual calls, not a checkout button.