Triple

T6447075
Position Surface form Disambiguated ID Type / Status
Subject Börte E138368 entity
Predicate spouse P13 FINISHED
Object Temüjin E355742 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: Temüjin | Statement: [Börte, spouse, Temüjin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Temüjin
Context triple: [Börte, spouse, Temüjin]
  • A. Temüjin chosen
    Temüjin is the birth name of Genghis Khan, the founder and first Great Khan of the Mongol Empire.
  • B. 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.
  • C. Yesün Temür
    Yesün Temür was a 14th-century Mongol ruler who served as Great Khan of the Mongol Empire and emperor of the Yuan dynasty in China.
  • D. Külüg Khan
    Külüg Khan was a Mongol emperor of the Yuan dynasty in China, known for his brief and financially troubled reign in the early 14th century.
  • E. Güyük Khan
    Güyük Khan was the third Great Khan of the Mongol Empire, ruling briefly in the 1240s and known for consolidating Mongol authority while facing internal dynastic tensions.
  • 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_69c008aa61ac8190bc96715ed79fe2d8 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0698edeac81909426902471d8a57b completed March 22, 2026, 10:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69c80299ee8c8190a64397339ae62119 completed March 28, 2026, 4:32 p.m.
Created at: March 22, 2026, 4:46 p.m.