Triple

T15806520
Position Surface form Disambiguated ID Type / Status
Subject Ögedei Khan E383229 entity
Predicate sibling P363 FINISHED
Object Chagatai 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: Chagatai Khan | Statement: [Ögedei Khan, sibling, Chagatai Khan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chagatai Khan
Context triple: [Ögedei Khan, sibling, Chagatai Khan]
  • A. Chagatai Khan chosen
    Chagatai Khan was the second son of Genghis Khan and the founder of the Chagatai Khanate, a major Mongol khanate in Central Asia.
  • B. 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.
  • C. Temür Khan
    Temür Khan was a Yuan dynasty emperor and grandson of Kublai Khan who ruled China and the Mongol Empire in the late 13th and early 14th centuries.
  • 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. Ugedei Khan
    Ugedei Khan was the third son of Genghis Khan and the second Great Khan of the Mongol Empire, under whose rule the empire reached its greatest territorial extent in Eurasia.
  • 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_69d86da2858c819090cc8481e7207b6e completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e0b52751348190964e82463ce9dd20 completed April 16, 2026, 10:08 a.m.
Created at: April 10, 2026, 4:48 a.m.