← All topics

Learn free · topic 32

Knowledge Graph Modelling

Knowledge Graph Modelling is the practice of representing information as a network of interconnected entities and relationships, enriched with semantic meaning. Instead of viewing data as isolated records stored in tables, this approach treats knowledge as a web of connections. Entities become nodes in a graph, and relationships between them become edges. The structure itself reflects how concepts are linked in the real world.

The primary goal of Knowledge Graph Modelling is to create a flexible and interconnected view of knowledge. By explicitly representing relationships, it becomes easier to integrate information from multiple sources, discover hidden patterns, and enable reasoning across domains. This modelling approach is especially valuable in environments where connections matter as much as individual data points.

A knowledge graph models the world as nodes and edges. Nodes represent entities such as Customer, Loan, or Product. Edges represent relationships such as applies for, owns, guarantees, or reviews. Unlike traditional relational models, where relationships are often embedded in foreign keys, the connections in a knowledge graph are first-class elements. They are visible, traversable, and central to the model.

To understand this more intuitively, consider a social network. A person is connected to friends, colleagues, and family members. If we want to find mutual friends or identify groups, we must follow the connections between people. The value lies not only in the individuals but in how they are connected. Knowledge Graph Modelling applies the same principle to business domains.

In a loan-processing environment, entities such as Customer, Loan Application, Approval Decision, Repayment, and Loan Officer can be represented as nodes. Relationships connect them: a Customer applies for a Loan Application; a Loan Application has an Approval Decision; a Loan Application is linked to a Repayment Schedule; a Loan Officer reviews a Loan Application. The graph itself becomes the model. Instead of hiding relationships inside tables, the structure of connections is explicit and central.

This explicit connectivity becomes even more powerful in analytical scenarios. Graph-based queries can answer questions that are difficult to solve using traditional models. For example, one might search for customers connected to delinquent loans within a specific time period. Another analysis might identify loan officers associated with higher-than-average delinquency rates. More advanced graph traversal techniques can detect fraud networks by following connections between guarantors, borrowers, and shared addresses. These insights emerge from exploring relationships, not just aggregating records.

Knowledge Graph Modelling is often supported by ontologies that define the meaning of nodes and relationships. While ontology modelling defines vocabulary and rules, the knowledge graph operationalizes those definitions into a living network of connected data. The graph structure allows reasoning engines to infer new relationships, classify entities, or detect patterns automatically.

The nature of Knowledge Graph Modelling is semantic and graph-structured. It is flexible and often described as schema-light, because new nodes and relationships can be added without redesigning rigid table structures. At the same time, it remains guided by ontologies to preserve consistency and meaning. Knowledge graphs are widely used in search engines, recommendation systems, fraud detection, enterprise data fabrics, and artificial intelligence applications. Their strength lies in treating relationships as primary modelling elements rather than secondary references.

In summary, Knowledge Graph Modelling moves beyond defining concepts and rules to building a connected intelligence layer. Where ontology provides shared meaning, the knowledge graph provides shared connectivity. By making relationships explicit and central, it enables discovery, reasoning, and advanced analytics across complex and interconnected domains.

Comparison

Technique

Focus

Loan Example

Representation

What it adds

FCO-IM

Facts and verbalization

“Customer 123 submits Loan Application 456 on 12-Aug” → fact type → role constraint

Preserves natural language → formal facts with traceability

Taxonomy

Classification-only (subset of ontology)

Loan Products → { Personal Loan, Home Loan, Auto Loan }

Simple hierarchies for categories, reporting, and navigation

Ontology

Shared meaning, categories, logic

Customer is a Person; LoanApplication hasApprovalDecision

Provides reasoning and consistency across systems

Knowledge Graph

Connected entities/relationships as first-class citizens

Customer → appliesFor → LoanApplication → hasDecision → Approval

Enables graph queries, relationship analysis, fraud detection, AI reasoning

Taxonomy is a simplified form of ontology (classification without full reasoning).

This table makes it explicit: FCO-IM = precise facts., Taxonomy = classification subset, Ontology = shared vocabulary and logic, and Knowledge Graph = dynamic, connected intelligence.

Finished reading? Test yourself with 10 questions on this topic.

Go to the questions →

From I Am Datapedia! by Mustafa Qizilbash, published here free by the author. Nothing about your reading is stored.