A Visual Guide

How Machines
Understand
the World

An introduction to ontologies and knowledge graphs — the invisible structures that teach computers to see meaning, not just data.

Scroll to explore
Act I — The Problem

Data is everywhere.
Understanding is nowhere.

We generate more data in a single day than most people could read in a lifetime. But data isn't knowledge. A spreadsheet of names doesn't know that Sarah is a person. A CRM entry doesn't understand that Acme Corp employs Sarah. And none of these systems know that Sarah just left Acme — which means the deal you're working on is now at risk.

📊 Spreadsheet
📧 Email
💬 Slack
📋 CRM
📝 Doc
📈 Report
🗂️ Database
📑 Invoice

Computers see text.
Humans see meaning.

When you read the word "Apple," your brain instantly draws on a web of relationships and context. You know whether we're talking about a fruit or a company based on the surrounding conversation. Computers don't do this naturally. To them, "Apple" is just a string of characters.

Apple
fruit
iPhone
Steve Jobs
pie
orchard
logo
company
Newton

What if we could give computers a map of how things relate to each other — not just data, but the structure of meaning itself? That's exactly what ontologies and knowledge graphs do.

Act II — The Blueprint

An ontology is a shared
vocabulary with rules.

An ontology is like an instruction manual for a domain of knowledge. It defines three things: the categories of things that exist, the relationships between them, and the rules that govern what's valid. Think of it as a shared language that both humans and machines can speak.

Classes

The nouns — categories of things that exist in your world

Properties

The verbs — how things connect and relate to each other

Constraints

The grammar — rules that keep the model coherent

Classes: the nouns of your world.

First, you define your classes — the types of things in your domain. A Person. An Organization. A Project. You can create hierarchies: an Employee is a type of Person. A Client is a type of Organization.

PersonOrganizationProjectEmployeeis a PersonContractoris a PersonClientis an OrgVendoris an OrgLocation

Properties: the verbs and adjectives.

Next come properties — the connections. Some link things to other things: "Sarah works at Acme Corp." Others attach descriptive values: "The project has a budget of $150,000."

works atleadshas projectSarahPersonAcme CorpOrganizationProject AtlasProjectbudget: $150k
Two types of properties: Object properties connect entities to entities (Sarah → works at → Acme). Data properties connect entities to values (Project Atlas → budget → $150k). Both are essential.

Constraints: the grammar.

Not every connection makes sense. A project doesn't "work at" a location — but it can be "located in" one. Constraints ensure that as your model grows, it stays coherent.

Attempting...
Project→ works at →Location
✓ Valid
Project→ located in →Location
Relationship matches the constraint rules.

Why bother? Because shared
understanding scales.

The power of an ontology is that it creates shared understanding. When everyone — humans and machines alike — agrees on what "customer" means, what "project" means, and how they relate, you can finally build systems that actually understand your world.

One person
A pair
A team
A department
An organization
Same vocabulary. Same rules. Same understanding.
Act III — The Building

From blueprint
to building.

An ontology is a blueprint. A knowledge graph is what happens when you fill that blueprint with real data. The ontology tells you what can exist. The knowledge graph shows you what does exist.

Ontology
The schema — abstract types and rules
PersonOrgProject
+ data
Knowledge Graph
Real entities and relationships
SarahAlexAcmeAtlasDevOps

Traversal: asking questions
by walking the graph.

To answer a question, you walk the graph. No keyword search. No SQL joins. Just follow the edges, and the answer assembles itself.

Query:"Who is working on projects for Acme Corp?"
has projectled bycollaboratesAcme CorpProject AtlasSarah ChenAlex Kim
1
Start at Acme Corp
2
Follow "has project" → Project Atlas
3
Follow "led by" → Sarah Chen
4
Follow "collaborates with" → Alex Kim

Inference: discovering what
nobody explicitly told you.

The real power is inference — discovering things nobody entered. If Sarah works at Acme, and Acme is headquartered in Chicago, we can infer Sarah is likely in Chicago. The graph didn't just store knowledge — it created new knowledge.

works atHQ inSarahAcme CorpChicago
Act IV — Why It Matters

You've been using
knowledge graphs for years.

These aren't abstract academic concepts. They're working behind the scenes in products you use every day.

🔍

Search Engines

Google's Knowledge Graph powers those instant answer panels. When you ask "How tall is the Eiffel Tower?" it doesn't search text — it looks up an entity.

🏥

Healthcare

Medical ontologies connect symptoms, diagnoses, treatments, and outcomes — helping systems catch what overworked doctors might miss.

🏢

Enterprise

Every organization has knowledge trapped in silos. Knowledge graphs connect people, projects, clients, and decisions across systems.

🏛️

Government

Tax codes, regulations, benefits — ontologies model the complex rules that govern public services, making them queryable and auditable.

From scattered data
to connected understanding.

Ontologies give machines a way to understand the structure of your world. Knowledge graphs fill that structure with everything you know. Together, they turn information into intelligence.

Not more data. Genuine understanding.

Part 1 of 3 — Next: Why your organization's knowledge is trapped

Stay in the loop

Get notified when we publish new content on organizational intelligence.

Visor
Ontologic guide

I’m Visor. Ask me about Ontologic — the platform, pricing, or how it fits your business.