Skip to content

Commit eca3c3b

Browse files
committed
Update context
1 parent a0a701f commit eca3c3b

File tree

1 file changed

+23
-2
lines changed

1 file changed

+23
-2
lines changed

overview/retrieval.md

Lines changed: 23 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -55,11 +55,32 @@ raw text snippets.
5555
## Ontology RAG
5656

5757
You have probably heard of GraphRAG before. Ontology RAG, much less likely.
58+
So, let's cover the basics.
59+
60+
### Ontologies
61+
62+
Ontologies are structured frameworks that formally define the concepts,
63+
relationships, and rules within a specific domain of knowledge. They provide a
64+
standardised vocabulary and logical structure for representing how entities
65+
relate to each other, enabling both humans and computers to share a consistent
66+
understanding of complex information. It's like a database schema, but
67+
for human knowledge.
5868

5969
In knowledge engineering, ontologies have a bad reputation - they are complex,
6070
take years to create, and people often have massive disagreements about what
61-
ontologies are there to do. But don't give up too soon, bringing Ontologies
62-
into information retrieval produces some awesome results.
71+
ontologies are there to do. Biologists famously disagree about what
72+
constitutes a 'cell'.
73+
74+
But this isn't to say there's 'flaw' - there's nothing broken about ontology
75+
technology. The real issue is that human knowledge is a profoundly complex
76+
experience. When we try to classify human knowledge, we can't eliminate the
77+
fundamental human experiences which come with trying to make sense of the
78+
world around us.
79+
80+
So, don't give up too soon, bringing ontologies into information retrieval
81+
produces some awesome results.
82+
83+
### Ontology RAG
6384

6485
Ontology RAG extends Graph RAG by incorporating domain ontologies to guide
6586
knowledge extraction. This approach is particularly valuable when working

0 commit comments

Comments
 (0)