Triple
T9542775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oghuz Yabgu State |
E230197
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Turkic state |
C18272
|
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 Turkic state Context triple: [Oghuz Yabgu State, instanceOf, medieval Turkic state]
-
A.
Turkish principality
chosen
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.
-
B.
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.
-
C.
Mongol successor state
A Mongol successor state is a political entity that emerged from the fragmentation of the Mongol Empire, inheriting its territories, institutions, and ruling elites while developing distinct regional identities and governance structures.
-
D.
Sultanate
A Sultanate is a form of monarchy or state ruled by a sultan, typically characterized by Islamic governance traditions and varying degrees of centralized authority.
-
E.
Turco-Mongol
Turco-Mongol refers to the historical synthesis of Turkic and Mongol political, military, and cultural traditions that shaped several Eurasian empires from the medieval to early modern periods.
- 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_69ca847c70b8819088a0a0bad64a50d6 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:01 p.m.