Triple

T6108495
Position Surface form Disambiguated ID Type / Status
Subject Borjigin E136172 entity
Predicate usedTitle P3254 FINISHED
Object Khagan E69977 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: Khagan | Statement: [Borjigin, usedTitle, Khagan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Khagan
Context triple: [Borjigin, usedTitle, Khagan]
  • A. Chanyu
    Chanyu was the imperial title used by the supreme rulers of the ancient Xiongnu confederation, a powerful nomadic empire in Central Asia.
  • B. Great Khan chosen
    The Great Khan was the supreme ruler of the Mongol Empire, holding ultimate authority over all Mongol khanates and conquests.
  • C. Batu Khan
    Batu Khan was a 13th-century Mongol ruler and military commander who founded the Golden Horde and led the Mongol invasions of Eastern Europe.
  • D. Khshayarsha
    Khshayarsha is the Old Persian name for Xerxes I, the powerful Achaemenid king who ruled the Persian Empire in the early 5th century BCE and led the invasion of Greece.
  • E. 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.
  • 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_69c0087dee9881909e3655be88208c01 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c05b835ed48190971c3ba397ca329f completed March 22, 2026, 9:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69c1255f03e08190b62cd8ca2c079afb completed March 23, 2026, 11:34 a.m.
Created at: March 22, 2026, 4:13 p.m.