Skip to content

Glossary

Knowledge graph

A knowledge graph represents entities and their relationships as connected, typed statements.

Knowledge fusion

A knowledge graph represents subjects and the relationships among them in a form that supports connected queries. Statements may describe types, attributes and links to other entities. A graph can be expressed using RDF or other graph models; the term alone does not imply a particular storage technology, ontology or level of factual reliability. Edges are still claims whose meanings depend on definitions and source context.

In practice, graphs help answer questions that cross record boundaries, such as which organizations sponsor trials associated with a compound. Stable identifiers and clear relationship definitions are essential. The same visible link may mean ownership, collaboration or mention, each with different consequences. A graph assembled from extraction also needs a way to represent uncertainty, time and provenance alongside the connection.

For defensible use, a path through the graph is a navigational aid, not proof that every edge is valid. Each material relationship should be traceable to evidence or a declared inference. Knowledge-base population supplies statements to a graph; ontology specifies meanings; entity resolution determines when nodes denote the same real-world thing.

Example

A fictional graph connects Halden Therapeutics AG to a fictional trial by a stated sponsor relationship, with the source notice attached to that edge.

The data model underneath

Most knowledge graphs reduce to statements in the form subject, predicate, object. In RDF the subject and predicate are identified by IRIs, the object is an IRI or a literal, and a set of such statements is a graph. A property graph model attaches key-value properties to nodes and edges, which makes it easy to annotate a relationship with a date or a source. The survey by Hogan and colleagues compares these models, together with query languages, schema languages, and the roles of identity and context, and is the standard overview. The SPARQL 1.1 query language is the W3C standard for querying RDF.

Meaning comes from two layers above the raw statements. A schema or ontology declares the types of entity and the relationships that may hold between them, and can support inference. Constraints, expressed for example in SHACL, check that data conform to the shapes the application expects. The article on OWL versus SHACL explains why the two are used for different purposes: one derives new statements under the open-world assumption, the other validates the data that is actually present.

What a graph does and does not guarantee

A graph guarantees structure, not truth. An edge between two nodes says that someone asserted a relationship; it says nothing about whether the assertion was correct, current or well sourced unless that information is stored with it. For that reason a graph used in decisions needs provenance on its statements, and the recent RDF 1.2 work on reifiers and triple terms is aimed at making such annotation a first-class feature; the article on RDF 1.2 provenance walks through what changes. The article on knowledge graph quality assessment argues that quality must be assessed against the decision the graph supports, not in the abstract.

Graphs also change. Identifiers must survive corrections, as discussed in the article on identifier versioning after corrections, and conclusions that depended on a retracted statement should be retracted with it, which is the subject of truth maintenance.

A worked example

A fictional graph holds the statement that Halden Therapeutics AG sponsors a named trial. A user asks which organisations are connected to a compound through trials. The graph answers by following the sponsor edge, and a second edge from the trial to the compound. A careful record attaches to the sponsor edge the registry entry that supports it and the date it was read, and to the compound edge the sentence in the protocol that names the compound. When the user asks why Halden Therapeutics AG appears in the answer, the system can show both source passages. If the registry later changes the sponsor, the edge is closed with an end date and the answer for the earlier period remains reproducible. The graph supports the navigation; the attached evidence supports the answer.

Related terms and boundaries

A knowledge graph is a container and a style of representation; what it contains is governed by neighbouring decisions. The ontology defines the vocabulary, entity resolution decides when two nodes are one, knowledge-base population supplies the statements, and the open-world assumption governs how a missing statement is read. A graph that stores statements without provenance can still answer questions, but cannot defend its answers, and the difference shows only when someone asks for the basis of a particular edge.

Checks a reviewer can run

Pick an edge and ask for its source, date and the activity that created it. Ask how contradicting edges are represented. Count edges with no provenance. Ask how a wrong edge is retracted and how answers that used it are found. Check that identifiers are stable and that merged nodes keep their old identifiers resolvable.

Common misreadings

  • Treating an edge as verified merely because it exists.
  • Collapsing distinct relationship types.
  • Joining nodes on name similarity alone.

Related terms

Appears in

Found an error on this page? See corrections for what counts as one, how to report it and the dated log.

Enquiry

Where does "Knowledge graph" bear on a decision of yours?

This entry sits under knowledge fusion. If a decision in your organization turns on it, send the entity concerned, the sources you fuse to describe it and who may read which of them. We reply with what a first record would cover.

Or write to [email protected] in your own words.