Triple

T10666781
Position Surface form Disambiguated ID Type / Status
Subject Middle zhuz E251376 entity
Predicate overlord P5603 FINISHED
Object Kazakh khans E260992 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: Kazakh khans | Statement: [Middle zhuz, overlord, Kazakh khans]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kazakh khans
Context triple: [Middle zhuz, overlord, Kazakh khans]
  • A. Khan-i-Khanan
    Khan-i-Khanan was the honorific title of the powerful Mughal regent and military commander Bairam Khan, who served as mentor and guardian to Emperor Akbar.
  • B. akim of Astana
    The akim of Astana is the government-appointed chief executive and administrative head of Kazakhstan’s capital city.
  • C. Kazakh Khanate chosen
    The Kazakh Khanate was a Turkic nomadic state that emerged in the 15th century on the Central Asian steppe and laid the political and cultural foundations of the Kazakh people.
  • D. Chagatai Khan
    Chagatai Khan was the second son of Genghis Khan and the founder of the Chagatai Khanate, a major Mongol khanate in Central Asia.
  • E. Great Khan
    The Great Khan was the supreme ruler of the Mongol Empire, holding ultimate authority over all Mongol khanates and conquests.
  • 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_69d6aa5b0d2881909584b20efc5877f0 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6f3204bac8190b9bd8bfcc705b06b completed April 9, 2026, 12:30 a.m.
NED1 Entity disambiguation (via context triple) batch_69d9885dc17881909df20abedd9da5e3 completed April 10, 2026, 11:31 p.m.
Created at: April 8, 2026, 9:08 p.m.