Triple
T14615168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buyantu Khan |
E343065
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Khagan of the Mongol Empire |
C7346
|
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: Khagan of the Mongol Empire Context triple: [Buyantu Khan, instanceOf, Khagan of the Mongol Empire]
-
A.
Chagatai khan
A Chagatai khan was a ruler of the Chagatai Khanate, a Mongol and later Turkic state in Central Asia founded by Chagatai, the second son of Genghis Khan.
-
B.
Mongol ruler
chosen
A Mongol ruler is a sovereign leader of the Mongol people and their empire, wielding military, political, and often spiritual authority over vast, multiethnic territories.
-
C.
Jurchen chieftain
A Jurchen chieftain is a hereditary or militarily ascendant leader of a Jurchen tribal group who exercises political, military, and economic authority within the broader context of Northeast Asian steppe-forest societies.
-
D.
Khan of Bukhara
The Khan of Bukhara is the sovereign ruler of the Khanate of Bukhara, a Central Asian polity historically centered in the city of Bukhara and exercising political, military, and religious authority over its territories.
-
E.
Khan of Khiva
The Khan of Khiva was the hereditary ruler of the Khanate of Khiva, a Central Asian polity centered in Khwarezm, who held political, military, and often religious authority over the region until its abolition in the early 20th century.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:25 a.m.