Triple
T22926784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toluid faction |
E569331
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mongol Empire faction |
C35130
|
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 faction Context triple: [Toluid faction, instanceOf, Mongol Empire faction]
-
A.
Mongol imperial dynasty branch
chosen
A Mongol imperial dynasty branch is a distinct ruling line or subdivision of the broader Mongol imperial family that governed a specific territory or khanate while sharing common ancestry and political heritage with the main Mongol Empire.
-
B.
institution of the Mongol Empire
An institution of the Mongol Empire is an organized structure or system—such as administrative offices, legal codes, military units, or religious frameworks—established by Mongol authorities to govern, manage, and integrate their vast, multiethnic empire.
-
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.
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.
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.
- 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_69e2458f7d008190901dccbaebeaba24 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:43 p.m.