Triple
T8683391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egrisi |
E206092
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Georgian kingdom |
C24866
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: medieval Georgian kingdom Context triple: [Egrisi, instanceOf, medieval Georgian kingdom]
-
A.
medieval Georgian principality
A medieval Georgian principality is a semi-autonomous territorial domain within the historical Kingdom of Georgia, ruled by a local prince or noble dynasty that exercised regional political, military, and economic authority while recognizing the suzerainty of a higher Georgian monarch or overlord.
-
B.
medieval Armenian kingdom
A medieval Armenian kingdom is a historically situated political entity in the Armenian Highlands, characterized by Armenian dynastic rule, Christian cultural identity, and feudal socio-political structures interacting with neighboring empires.
-
C.
early medieval kingdom
An early medieval kingdom is a territorially bounded, monarch-led polity emerging after the fall of the Western Roman Empire, characterized by decentralized power, personal lordship ties, and a fusion of Roman, Germanic, and Christian traditions.
-
D.
medieval duchy
A medieval duchy is a territorial domain ruled by a duke or duchess, typically semi-autonomous within a larger kingdom or empire, with its own feudal hierarchy, laws, and military obligations.
-
E.
Armenian principality
An Armenian principality is a semi-autonomous political entity historically governed by Armenian nobility, exercising regional authority under varying degrees of dependence on larger empires or kingdoms.
- F. None of above. chosen
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ca835379688190aa06b9d98e684d58 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:32 p.m.