Triple
T16051808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinggisid imperial ideology |
E389369
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mongol Empire ideology |
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: Mongol Empire ideology Context triple: [Chinggisid imperial ideology, instanceOf, Mongol Empire ideology]
-
A.
Mongol conquest
The Mongol conquest refers to the series of 13th- and 14th-century military campaigns by the Mongol Empire that rapidly expanded its rule across Eurasia through highly mobile warfare, psychological tactics, and administrative integration of conquered peoples.
-
B.
Mongol law
Mongol law refers to the legal principles, customary practices, and codified regulations—most notably the Yassa—developed under the Mongol Empire to govern its diverse subjects, maintain military discipline, and ensure social order across vast conquered territories.
-
C.
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.
-
D.
Mongol imperial council
The Mongol imperial council was a high-level advisory and decision-making body of Mongol rulers, composed of princes, generals, and nobles who deliberated on matters of war, governance, succession, and law.
-
E.
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.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:56 a.m.