Triple

T16129287
Position Surface form Disambiguated ID Type / Status
Subject Güyük Khan E391350 entity
Predicate associatedWith P37 FINISHED
Object Batu 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: Batu Khan | Statement: [Güyük Khan, associatedWith, Batu Khan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Batu Khan
Context triple: [Güyük Khan, associatedWith, Batu Khan]
  • A. Batu Khan chosen
    Batu Khan was a 13th-century Mongol ruler and military commander who founded the Golden Horde and led the Mongol invasions of Eastern Europe.
  • B. Erlik Khan
    Erlik Khan is a deity from Turkic and Mongolic mythology, commonly regarded as the god of death and ruler of the underworld.
  • C. 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.
  • D. 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.
  • 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_69d87f1bb0988190b490d273dbf3fd03 completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e202075860819088d27d921609a6ce completed April 17, 2026, 9:48 a.m.
Created at: April 10, 2026, 5:01 a.m.