← Back to concept explainers

Concept Fable

Knowledge graph

Conclusion first:A Knowledge Graph uses entities, relationships, and attributes to represent knowledge in a structured way. It explicitly models "who has what relationship with whom," and is often used for entity queries, causal/dependency relationship analysis, compliance traceability, recommendations, Graph RAG, and complex question answering. Unlike relying only on text chunks or vector similarity, a knowledge graph excels at handling multi-hop relationships, structured constraints, and explainable paths, but its construction cost is higher, requiring entity extraction, relationship extraction, schema/ontology design, and continuous maintenance.

Knowledge Graph · Knowledge representation

Read the story first. There is no rush to give a definition here; let the question grow on its own first.

Fable

The archive drew the relationships between names

The city archive used to store materials by volume. One book for caravans, one for the docks, one for taxes, one for bridges. Each book could be searched, but many questions spanned across books.

One day, the mayor asked: 'Why did last year's East Bridge maintenance affect South Port tax revenue?' The copyist found the East Bridge maintenance records and also found the South Port tax ledgers, but could not explain how the two were connected.

Someone suggested memorizing all the files. The curator shook his head. Another person suggested putting more tags on each book: East Bridge, South Port, taxes, repairs, caravans. Once there were more tags, relevant books could be found, but the relationships were still unclear.

Later, an old clerk changed his approach. He no longer only registered scrolls, but broke the city's things into individual names: East Bridge, South Port, March caravan, temporary detour, bridge repair order, tax decline. Then he drew lines between the names: East Bridge repair caused the caravan to detour, the caravan detour reduced South Port stops, and fewer stops affected tax revenue.

At first everyone found this troublesome. The old secretary said: the case file tells you that something exists; the relationships tell you why things are connected.

A few days later, the mayor asked again: 'If the East Bridge is repaired again next year, which docks and merchants are most likely to be affected?' This time the scribe did not flip through a pile of books, but walked along the lines on the map, from the East Bridge to the detour route, then to caravans, docks, merchants and tax categories.

They also discovered that certain lines on the map needed source annotations. Some came from regulations, some from contracts, and some were merely a historical event. Lines differ in credibility, and inferences differ in weight.

Later, the archive no longer only asked 'which book mentions this word,' but also 'which entities is this entity related to, what are the relationships, where is the evidence, and how far can it be inferred.' Only then did the townspeople understand: some knowledge is not a passage of text but a network of entities and relationships. To answer complex questions, one must be able to walk along this network. Later the archive hung the graph in the front hall, and merchants could also add relationships. The old clerk did not accept everything wholesale; every new line had to note its source, time, and level of credibility. Because one wrong line could skew many inferences, more dangerous than a misplaced book. The larger the graph, the more the archive valued verification and updates; as long as relationships stay alive, answers will not remain stuck in the old city's appearance.

Reveal

This story is about: knowledge graphs

A Knowledge Graph uses entities, relationships, and attributes to represent knowledge in a structured way. It explicitly models "who has what relationship with whom," and is often used for entity queries, causal/dependency relationship analysis, compliance traceability, recommendations, Graph RAG, and complex question answering. Unlike relying only on text chunks or vector similarity, a knowledge graph excels at handling multi-hop relationships, structured constraints, and explainable paths, but its construction cost is higher, requiring entity extraction, relationship extraction, schema/ontology design, and continuous maintenance.

What matters is that it is not just a term, but a structural problem that repeatedly appears in real AI / Agent systems. Understanding it lets you judge when to add a model, when to change a process, and when to add governance.

Metaphor mapping

  • Individual case files: unstructured documents or an ordinary knowledge base
  • More tags: keywords and categories help with finding, but cannot express relational structure
  • East Bridge, South Port, caravans, taxes: entity nodes
  • Maintenance causes detours, detours affect stops: relationship edges
  • The source and credibility of the lines: relationship evidence, provenance, confidence, and governance requirements
  • Follow the lines on the graph: graph queries, multi-hop reasoning, and relationship traversal
  • Which docks and merchants are affected: knowledge graphs suit dependency chains, impact analysis, and complex Q&A
  • A network of entities and relationships: the core representation of a Knowledge Graph

Andy Ren Xu's judgment

The practical value of this concept is that it helps you break "AI features that look smart" into deliverable, verifiable, and governable units of work.

entitiesrelationshipsontologytriplesRDFgraph databaseGraph RAG
京ICP备2026014272号