Triple

T16591369
Position Surface form Disambiguated ID Type / Status
Subject Ejei Khan E403093 entity
Predicate predecessor P97 FINISHED
Object Ligdan 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: Ligdan Khan | Statement: [Ejei Khan, predecessor, Ligdan Khan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ligdan Khan
Context triple: [Ejei Khan, predecessor, Ligdan Khan]
  • A. Ligdan Khan chosen
    Ligdan Khan was the last grand khan of the Mongol Northern Yuan dynasty, known for his attempts to resist Manchu expansion and preserve Mongol independence in the early 17th century.
  • B. Bayanchur Khan
    Bayanchur Khan was an 8th-century ruler who greatly expanded and consolidated the Uyghur Khaganate, turning it into a powerful Central Asian empire.
  • C. Erlik Khan
    Erlik Khan is a deity from Turkic and Mongolic mythology, commonly regarded as the god of death and ruler of the underworld.
  • 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 (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_69d88387363c8190a97a0c942130de97 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e359a012e081909a0604dde3c04bbb completed April 18, 2026, 10:14 a.m.
Created at: April 10, 2026, 5:16 a.m.