Triple
T14615166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buyantu Khan |
E343065
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | emperor of the Yuan dynasty |
C13056
|
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: emperor of the Yuan dynasty Context triple: [Buyantu Khan, instanceOf, emperor of the Yuan dynasty]
-
A.
emperor of China
chosen
The emperor of China was the supreme hereditary ruler of imperial China, regarded as the Son of Heaven and the ultimate political, military, and ritual authority over the Chinese empire.
-
B.
Mongol ruler
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.
Ming dynasty emperor
A Ming dynasty emperor is the supreme hereditary ruler of China during the Ming period (1368–1644), wielding ultimate political, military, and ritual authority as the Son of Heaven within a centralized bureaucratic state.
-
D.
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.
-
E.
Yuan dynasty court
The Yuan dynasty court was the central governing institution of the Mongol-ruled Chinese empire, where the emperor and his officials conducted political, military, and ceremonial affairs that integrated Mongol and Chinese traditions.
- 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.