Facilitator guide · All courses

Discussion Guide

Questions to run after each knowledge check or exercise, with notes on what to listen for. The checks test recall. The discussion is where the ideas attach to the participants' own work.

How to use it. Run the check or exercise first, then pick two or three prompts from its section. Give the room a minute of silence before anyone answers. Open "What to listen for" only on the facilitator's screen.

Prompts are written for the participants. The notes are written for you.

1 minsilent thinking
5 minpairs or tables
8 minwhole room
1 minone sentence each to close
Knowledge Graph Foundations · Week 1

Forms, Sets & Worlds

Open the check →

Plato's forms, sets and hierarchy, classes and instances, and the difference between an open world and a closed one.

Prompts

What to listen for
  • Confusion between a class and a role. "Supplier" is often a role a Company plays, not a kind of Company. Ask: can the same thing stop being one without ceasing to exist?
  • Closed-world assumptions hidden in reports. A dashboard that shows "no incidents" when the feed was down is a closed-world reading of open-world data.
  • Hierarchies built for convenience rather than truth. If inheritance breaks, the parent is usually wrong, not the child.
  • Nobody can name the owner of a definition. That is the gap an ontology is meant to fill.
Knowledge Graph Foundations · Exercise

The CQ Forge

Open the exercise →

Competency questions: the questions a knowledge graph must be able to answer, and how a good one decomposes into classes, properties, controlled values and rules.

Prompts

What to listen for
  • Questions that are really reports. "Show me all orders" is a lookup with no decision behind it. Push for the decision the answer would change.
  • Vague quantifiers: "important customers", "recent issues". Each one hides a controlled value or a rule that someone must define.
  • Inference questions disguised as lookups. "Which suppliers are at risk?" needs a rule for risk before it needs any data.
  • The group realising the same question is asked in three departments with three different meanings. Link this to Domain Detective.
Business course · Exercise 1

Domain Detective

Open the exercise →

Ten words that appear in every domain, and the domain-specific words that finally settle which world you are in. The label did not carry the meaning. The schema did.

Prompts

What to listen for
  • Stories about integration projects that failed on vocabulary rather than technology. Two systems with a "settlement date" that could not be compared.
  • The instinct to solve it by picking one definition for everyone. Sometimes right, often not. An ontology can hold both meanings as two concepts with two labels.
  • Participants noticing that the general words were true but useless. This is the case for specialisation: description lives in the specific tiers.
  • Anyone claiming their domain has no ambiguous terms. Ask them to define "customer".
Business course · Exercise 2

Ontology Builder

Open the exercise →

A blueprint of concepts, hierarchy, relations and attributes, then data that the blueprint checks. Participants built their own, from a blank page.

Prompts

What to listen for
  • Frustration at the refusal. Good. That is a schema doing its job, and the same friction is what keeps bad data out of a real graph.
  • Blueprint changes described as routine. If the T-Box changes as often as the A-Box, the model is not settled and every report built on it is at risk.
  • Attribute-versus-concept arguments. The useful test: does it need its own identity and relations? A colour is an attribute. A supplier is a concept.
  • People discovering that their ontology looks like their org chart. Ask whether the world is really shaped like the reporting lines.
Business course · Exercise 3

Ask the Graph

Open the exercise →

One query language, SPARQL, pointed at the data, then at the blueprint, then at both in one query. Everything was a standard, and the graph came out of the builder unchanged.

Prompts

What to listen for
  • The moment someone says the ontology "is just more data". That is the lesson landing. Ask what it means for governance if the schema is versioned and queried like a table.
  • Lock-in stories: a platform that could not export its own model, a query language nobody else speaks. Contrast with the file that moved between the builder and this page untouched.
  • Discomfort with the empty classes. Modelling ahead of data is normal; the point is that the graph can tell you where it happened.
  • Anyone equating "graph database" with the standards. Be precise: property-graph products are a separate family with their own ISO query language, GQL; the W3C stack is the one with open vocabulary standards and vendor-neutral files.

Closing the session

Each participant writes three lines and reads them aloud. No discussion, just the reading.

  1. One concept my organisation needs to define and does not.
  2. One relation between two things we talk about but never record.
  3. One question we would ask tomorrow if the graph could answer it.

Collect the lines. They are the seed of a real competency-question list and a real T-Box, written by the people who will use it.