Triple
T14615186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buyantu Khan |
E343065
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | Gegeen Khan |
E449175
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Gegeen Khan | Statement: [Buyantu Khan, successor, Gegeen Khan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gegeen Khan Context triple: [Buyantu Khan, successor, Gegeen Khan]
-
A.
Gegeen Khan
chosen
Gegeen Khan was a 14th-century Mongol ruler who served as the Yuan dynasty emperor and nominal Great Khan of the Mongol Empire.
-
B.
Ejei Khan
Ejei Khan was the final khan of the Northern Yuan dynasty, whose surrender to the Qing marked the end of Mongol imperial rule in Mongolia.
-
C.
Biligtü Khan
Biligtü Khan was a 14th-century Mongol emperor of the Northern Yuan dynasty who ruled in Mongolia after the fall of the Yuan dynasty in China.
-
D.
Kerei Khan
Kerei Khan was a 15th-century Kazakh leader recognized as one of the first khans and a founding figure of the Kazakh Khanate.
-
E.
Hülegü Khan
Hülegü Khan was a 13th-century Mongol ruler and grandson of Genghis Khan who founded the Ilkhanate in Persia and led the conquest of Baghdad, ending the Abbasid Caliphate.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_69deb45264988190a1df13e8b54a85bd |
completed | April 14, 2026, 9:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffcf0743288190b3bec8c48b5c7893 |
completed | May 10, 2026, 12:19 a.m. |
Created at: April 10, 2026, 1:25 a.m.