Triple
T14855171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mongol-ruled Central Asia |
E349332
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | territory of the Mongol Empire |
C22037
|
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: territory of the Mongol Empire Context triple: [Mongol-ruled Central Asia, instanceOf, territory of the Mongol Empire]
-
A.
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.
-
B.
Eurasian empire
A Eurasian empire is a vast, centralized political entity that spans significant territories across both Europe and Asia, integrating diverse cultures, economies, and governance systems under a single imperial authority.
-
C.
nomadic empire
chosen
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.
-
D.
Eurasian steppe
The Eurasian steppe is a vast belt of temperate grassland stretching from Eastern Europe across Central Asia to Manchuria, characterized by open plains, continental climate, and a long history of nomadic pastoralism and cultural exchange.
-
E.
Cossack territory
Cossack territory is a semi-autonomous frontier region historically inhabited and governed by Cossack communities, characterized by military service, self-rule, and a distinct cultural identity within larger empires.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:54 a.m.