Triple
T4957815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Principality of Samtskhe |
E111329
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Georgian principality |
C16683
|
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 principality Context triple: [Principality of Samtskhe, instanceOf, medieval Georgian principality]
-
A.
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.
-
B.
Russian principality
A Russian principality is a semi-autonomous medieval or early modern territorial state ruled by a prince within the broader political and cultural sphere of Rus', often owing allegiance to a grand prince or tsar.
-
C.
medieval East Slavic state
A medieval East Slavic state is a historically situated political entity formed by East Slavic peoples between the 9th and 15th centuries, characterized by princely rule, Orthodox Christianity, and a feudal socio-economic structure.
-
D.
Catalan principality
A Catalan principality is a medieval or early modern political entity in which Catalan-speaking territories were governed by a prince or similar sovereign authority, often within larger composite monarchies.
-
E.
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.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:32 p.m.