Triple

T15610800
Position Surface form Disambiguated ID Type / Status
Subject Toghon Temür E375283 entity
Predicate successor P78 FINISHED
Object Biligtü Khan E1172820 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: Biligtü Khan | Statement: [Toghon Temür, successor, Biligtü Khan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Biligtü Khan
Context triple: [Toghon Temür, successor, Biligtü Khan]
  • A. Biligtü Khan chosen
    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.
  • B. Gegeen Khan
    Gegeen Khan was a 14th-century Mongol ruler who served as the Yuan dynasty emperor and nominal Great Khan of the Mongol Empire.
  • C. 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.
  • 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. Kuchum Khan
    Kuchum Khan was the last khan of the Siberian Khanate, known for resisting Russian expansion into Siberia in the late 16th century.
  • 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_69d85ccf2794819096cda4cbcb02d478 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04e8024948190a6c711f2e5c2aac4 completed April 16, 2026, 2:50 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0313aa65a481909707b1e7a6d6ce6f completed May 12, 2026, 11:48 a.m.
Created at: April 10, 2026, 4:13 a.m.