Triple

T18458608
Position Surface form Disambiguated ID Type / Status
Subject Yesün Temür E450970 entity
Predicate predecessor P97 FINISHED
Object Gegeen Khan NE NERFINISHED

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: [Yesün Temür, predecessor, Gegeen Khan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gegeen Khan
Context triple: [Yesün Temür, predecessor, 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. Güshi Khan
    Güshi Khan was a 17th-century Oirat Mongol leader who founded the Khoshut Khanate in Tibet and played a key role in establishing the Dalai Lama’s political authority.
  • E. 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.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8d38345688190b565eac2e4cd7935 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e52a7c18d88190ac17f58111722223 completed April 19, 2026, 7:18 p.m.
Created at: April 10, 2026, 11:31 a.m.