Triple

T14554839
Position Surface form Disambiguated ID Type / Status
Subject Biligtü Khan Ayushiridara E341510 entity
Predicate reignTitle P10605 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: [Biligtü Khan Ayushiridara, reignTitle, Biligtü Khan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Biligtü Khan
Context triple: [Biligtü Khan Ayushiridara, reignTitle, 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. Kuchum Khan
    Kuchum Khan was the last khan of the Siberian Khanate, known for resisting Russian expansion into Siberia in the late 16th century.
  • E. Erlik Khan
    Erlik Khan is a deity from Turkic and Mongolic mythology, commonly regarded as the god of death and ruler of the underworld.
  • 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_69d822db9c8481908213ceb39585f792 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb2f00cec8190a7b6482d18b9a216 completed April 14, 2026, 9:34 p.m.
NED1 Entity disambiguation (via context triple) batch_69ff82dfbc28819090cf56f16b5e7c39 completed May 9, 2026, 6:54 p.m.
Created at: April 10, 2026, 1:23 a.m.