Twelve weeks, from first triple to deployed knowledge graph.

RDF, OWL, SPARQL, and modern knowledge graphs — from first principles to a deployed hybrid LLM + knowledge graph application. Every artifact, note, and stumbling point published as I go.

Duration
12 weeks · 4 modules
Effort
~5–7 hours / week
Author
Barbara Hidalgo-Sotelo
Module 1 · in progress — launched May 31, 2026
Abstract knowledge-graph illustration in cream, amber, and teal — nodes joined by dashed connections.
The arc

Four modules, one deeper arc.

The curriculum moves through the semantic web stack, from RDF foundations to a deployed hybrid system. Along the way, each module sharpens a different act of sensemaking: naming things, organizing them into types, qualifying claims, and using structured knowledge in practice.

The modules move forward through the technical stack while returning to a familiar pattern: naming, categorizing, justifying, and knowing.

Diagram titled From naming to knowing. Four modules move from Foundations to Modeling to Reasoning to Shipping. The conceptual arc is naming, categorizing, justifying, and knowing.
What I’ll learn

The semantic web stack, layered.

Each layer builds on the one below it. The curriculum walks up the stack in order: triples first, schemas next, ontologies and reasoning after that. SPARQL is the query language that runs across all layers.

The semantic web stack Layered diagram showing RDF at the bottom, then RDFS, OWL, SHACL, and Applications at the top, with SPARQL running vertically through all layers. RDF triples · URIs · the graph RDFS classes · subclasses · domain/range OWL restrictions · equivalence · reasoning SHACL constraints · validation · shapes Applications hybrid retrieval · KG explorer SPARQL — queries through all layers Built bottom up
The anchoring projects

Two existing projects as canvases.

Two projects I’d already built turned out to be ideal canvases for this material — which is half the reason the curriculum exists. The first is a character network from an anime I love, Naruto: its ranks, villages, and contested fan canon make surprisingly rich ground for real ontology design. The second is a knowledge graph of my own resume and skills — practical, since I’m consulting and job-hunting, and a sharp test case because its skill taxonomy already speaks SKOS.

Primary canvas

Naruto Network Graph

A character network from anime subtitle data — 87 characters across three story arcs, with hand-coded canonical relationships layered over co-appearance edges. The rich categorical structure of the Naruto universe (ninja ranks, villages, jutsu, contested fan canon) makes it an unusually good semantic-web testbed. Pop-culture domains are standard in ontology pedagogy: the Pizza ontology is the canonical Protégé tutorial for the same reason.

87 characters 3 arcs 36 canonical relationships

Explore the Naruto graph →

Module 1 anchor

Resume Graph Explorer

A career graph with ESCO/SKOS integration — existing Neo4j implementation with skill taxonomy linked to the European Skills, Competences, Qualifications and Occupations vocabulary. The reason it anchors Module 1: ESCO is already a SKOS vocabulary, which means the case for RDF over a labeled property graph is exceptionally sharp here. Returns in Module 3 as a venue for skill inference work.

Neo4j + Cypher SKOS + ESCO Module 1 + 3

Open the Resume Graph Explorer →

The two projects are useful in opposite ways. Naruto's world is densely categorical — ranks, villages, jutsu types, contested fan canon — which is the raw material that ontology modeling and reasoning feed on, so it carries Modules 2 and 3. The Resume Graph is the other kind of useful: its skills already map to ESCO, a published vocabulary, so it makes the foundational case for linked data concrete instead of toy — which is why it anchors Module 1.

The repository

Everything lives here.

The GitHub repository is the canonical record. Syllabus, weekly progress, exercises, ontologies, notes, and published artifacts all live in one place. Visitors land on the README; followers track PROGRESS.md for weekly updates.

// dagny099/semantic-web-curriculum ├── README.md // repo front door ├── SYLLABUS.md // full 12-week curriculum ├── PROGRESS.md // live weekly tracker ← start here ├── REFLECTIONS.md // cross-module learnings (coming soon) ├── modules/ │ ├── 01-foundations/ // ← in progress │ │ ├── README.md // module hub │ │ └── submodules/ // synthesis pages + workbooks │ ├── 02-modeling/ │ ├── 03-reasoning/ │ └── 04-shipping/ ├── resources/ │ ├── reading-list.md │ ├── tools.md │ └── public-kgs.md └── // site pages: map · glossary · roadmap
What’s next

Coming as each module lands.

These slots will fill in as each module produces its artifacts. Listed here so the structure is visible from day one and the work has clear targets. Track what’s shipped and what’s next on the roadmap.

Interactive · Module 1

SPARQL playground for ESCO queries

Embedded query editor with sample queries from the Resume Graph Explorer comparison. Run live against a public endpoint.

Visualization · Module 2

Naruto ontology in WebVOWL

Interactive class hierarchy explorer rendered from the published Turtle. Click any node to see properties and instances.

Video · End of Module 2

Designing an ontology in 3 hours

Time-lapse screen recording of the actual modeling work. The wrong turns visible. Less polish than tutorial videos; more honesty.

Interactive · Module 3

Reification approaches, compared

Side-by-side: same fact expressed in classical RDF reification, n-ary, named graphs, RDF-star. Toggle between styles.

Deployed demo · Module 4

Naruto Knowledge Graph Explorer

Public web app. Ask natural-language questions, see generated SPARQL, explore character networks with ontology overlay.

Dashboard · ongoing

Live progress dashboard

Auto-generated from PROGRESS.md commit history. Modules completed, artifacts shipped, current focus. Embedded on homepage.

Required reading

The canonical references.

None of the conceptual content in the curriculum is original; the contribution is the path through it. These are the books and specs the curriculum points to repeatedly. The full bookmark set lives in resources/reading-list.md.

01
Semantic Web for the Working Ontologist
Allemang, Hendler & Gandon · 3rd edition · ACM Books 2020 · workingontologist.org
Book
02
Learning SPARQL
Bob DuCharme · 2nd edition · O’Reilly 2013 · learningsparql.com
Book
03
Knowledge Graphs
Hogan, Blomqvist, Cochez, et al. · Synthesis Lectures · 2021 · kgbook.org
Open Access
04
Linked Data: Evolving the Web into a Global Data Space
Heath & Bizer · linkeddatabook.com
Open Access
05
W3C Specifications
RDF 1.1 Primer · Turtle · SPARQL 1.1 · OWL 2 Primer · SHACL · SKOS · w3.org/TR
Primary source
About the project

One practitioner, working openly.

This curriculum is published under Sensemaking AI, an independent AI and machine learning consulting practice. It’s run solo by Barbara Hidalgo-Sotelo — cognitive scientist, AI/ML consultant, Toastmaster, marathon runner, beekeeper, and longtime builder of quirky-but-rigorous data projects.

Two web homes, two different jobs. barbhs.com is the technical portfolio — projects, experiments, the body of work. sensemaking-ai.com is the practice — applied AI work for people and organizations who want to think clearly with AI, not just move faster because of it.

The curriculum sits between them. It’s how the technical body of work gets developed in the open — redos, failed exercises, and wrong turns included, because the process is more useful than a polished finished state. More on why I work this way is in the launch note.

Follow along on GitHub for the canonical record and LinkedIn for twice-weekly progress; longer essays land on sensemaking-ai.com.

Questions, corrections, and discussion welcome via the repository’s issues. Pull requests on the curriculum itself aren’t accepted — this is a personal learning project — but disagreements about design choices are always interesting.

Exploring messy data, intelligent systems, and what it means to make meaning — through the lens of a cognitive scientist who builds things people actually use.