Triple
T3815720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kok-boru |
E84249
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Central Asian game |
C10983
|
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: Central Asian game Context triple: [Kok-boru, instanceOf, Central Asian game]
-
A.
Central Asian title
A Central Asian title is an honorific or formal designation historically used across Central Asia to denote rank, authority, or social status among rulers, nobles, religious leaders, and other prominent figures.
-
B.
Central Asian polity
A Central Asian polity is a political entity—such as a state, khanate, emirate, or tribal confederation—centered in the Central Asian region, shaped by its steppe geography, Silk Road connections, and interactions among Turkic, Persian, Mongol, and other cultural influences.
-
C.
Central Asian polity
A Central Asian polity is a historically or contemporarily organized political entity—such as a state, khanate, or empire—centered in the Central Asian region, characterized by its governance structures, territorial control, and interactions with neighboring powers.
-
D.
Central Asian cultural practice
chosen
A Central Asian cultural practice is a traditional social or ritual activity rooted in the histories, beliefs, and daily lives of peoples from the Central Asian region, often expressed through customs, arts, and communal gatherings.
-
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_69aed931f5908190be2c07af66d4df25 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.