Triple
T32087488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shibanid dynasty |
E819488
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Genghisid dynasty |
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: Genghisid dynasty Context triple: [Shibanid dynasty, instanceOf, Genghisid dynasty]
-
A.
Mongol royal house
The Mongol royal house is the ruling lineage descended from Genghis Khan that governed the Mongol Empire and its successor states, holding supreme political, military, and symbolic authority over Mongol domains.
-
B.
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.
-
C.
Golden Horde khan
A Golden Horde khan is the supreme ruler of the Mongol-Turkic Golden Horde state, wielding military, political, and economic authority over its territories and vassals.
-
D.
khans of the White Horde
Khans of the White Horde were the ruling nomadic Turkic-Mongol sovereigns of the eastern Jochid ulus, governing steppe territories in Central Asia and Siberia as part of the wider Mongol Empire’s successor states.
-
E.
Tatar khanate
The Tatar khanate is a historical political entity ruled by Tatar khans, typically emerging from the fragmentation of larger steppe empires and characterized by a nomadic or semi-nomadic elite, Turkic-Mongol cultural influences, and control over key trade and military routes.
- 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:25 a.m.