liveBook · Manning

Knowledge graph

As explained in Context Engineering

A graph-structured representation of entities and their relationships.

A knowledge graph represents domain entities and their relationships explicitly, giving retrieval a structured alternative to unstructured documents or isolated vector embeddings. Graph-based retrieval can follow linked relationships rather than returning only separate text fragments. section 3.3

A graph combines three core elements:

  • Nodes represent entities; edges connect them through named relationships; properties attach descriptive attributes to nodes or edges. section 3.3.1
  • Labeled property graphs store linked facts with attributes. RDF graphs represent knowledge as triples and can use ontologies to define schema and support inference. section 3.3.1
  • RDF offers semantic consistency, interoperability, and richer provenance, at the cost of greater modeling and operational complexity. section 3.3.1

Simple relationship

A graph can connect a product to an organization with a “manufactures” edge, and attach attributes such as identifiers or provenance. section 3.3.1

How Context Engineering covers it

How deep it goes
Defines graph elements and compares property graphs with RDF, including RDF trade-offs and inference.
Examples
Uses people, organizations, products, and locations as entities, with relationships such as “manufactures” and “located in.”
What you can do after
Understand how graph structure supports linked retrieval and how property graphs differ from RDF.
How it connects
Connects to retrieval-augmented generation, vector embeddings, RDF, labeled property graphs, and ontologies.

Also explained in

Compare how 15 books explain knowledge graph →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Context Engineering. The section links point to the parts of the book it draws on.