Triple
T14468733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cuman–Kipchak confederation |
E358781
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Turkic tribal union |
C8668
|
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: Turkic tribal union Context triple: [Cuman–Kipchak confederation, instanceOf, Turkic tribal union]
-
A.
Oghuz Turkic polity
An Oghuz Turkic polity is a socio-political entity formed by Oghuz Turkic groups, typically characterized by tribal confederation structures, nomadic or semi-nomadic lifeways, and rule by military-elite lineages asserting authority over diverse subject populations.
-
B.
tribal confederation
chosen
A tribal confederation is a loose alliance of distinct tribes that cooperate for mutual defense, governance, or shared interests while retaining their individual identities and autonomy.
-
C.
Turkish principality
A Turkish principality is a semi-independent, territorially defined political entity ruled by a Turkish dynastic leader, typically emerging in the medieval or early modern period within the broader context of Turkic state formation and regional power dynamics.
-
D.
nomadic empire
A nomadic empire is a large, often militaristic polity built and ruled by mobile pastoral or steppe peoples who control vast territories and diverse sedentary populations without fully settling them.
-
E.
Oghuz Turkic tribe
An Oghuz Turkic tribe is a socio-political and kinship-based group descended from the historical Oghuz Turks, sharing common lineage, language, and cultural traditions within the broader Oghuz Turkic world.
- F. None of above.
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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:20 a.m.