{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreignutllhh4vf7bsjshkjxatbvgsrha7zzu2cuotnvlnfj5tdg5lsm",
    "uri": "at://did:plc:3peywwdnn4jkfvqowpviodbf/app.bsky.feed.post/3mp3ionu6puy2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreihcpqprfcyqq6pfg2kvw34oosx3pkdoqmoczuugmyyqyq3udk4wjy"
    },
    "mimeType": "image/png",
    "size": 339781
  },
  "path": "/blog/2026/06/23/what-is-a-knowledge-graph/",
  "publishedAt": "2026-06-23T00:00:00.000Z",
  "site": "https://jeffbailey.us",
  "tags": [
    "Data Engineering",
    "AI Engineering",
    "Software Architecture"
  ],
  "textContent": "Most data starts as rows in tables: customers, orders, tickets. To see how a customer links to a product they refunded through a support ticket, you write joins. The connections exist, but the tables hide them; they surface only when you go looking.\n\nA knowledge graph puts those connections first, treating the relationships between entities as the main thing. By the end of this article, you’ll know what a knowledge graph is, why people build them, how one works, and where it helps and where it doesn’t.",
  "title": "What Is a Knowledge Graph?"
}