Triple

T15806518
Position Surface form Disambiguated ID Type / Status
Subject Ögedei Khan E383229 entity
Predicate child P120 FINISHED
Object Shiremun E337417 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: Shiremun | Statement: [Ögedei Khan, child, Shiremun]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shiremun
Context triple: [Ögedei Khan, child, Shiremun]
  • A. Shiremun chosen
    Shiremun was a 13th-century Mongol prince of the Borjigin dynasty and a grandson of Genghis Khan through his father Ögedei Khan.
  • B. Shinjo
    Shinjo is a notable figure associated with the Kegon school of Japanese Buddhism, recognized for contributions to its teachings or development.
  • C. Shinshiro
    Shinshiro is a city in eastern Aichi Prefecture, Japan, known for its mountainous scenery, historic battle sites, and traditional rural landscapes.
  • D. Munefusa
    Munefusa is the birth name of Matsuo Bashō, the renowned 17th-century Japanese haiku poet and travel writer.
  • E. Sumirago
    Sumirago is a small town in the Lombardy region of northern Italy, known in fashion circles as the longtime base of the Missoni design house.
  • 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_69d86da2858c819090cc8481e7207b6e completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e0b52751348190964e82463ce9dd20 completed April 16, 2026, 10:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff998fa5588190b28efc2f342405aa completed May 9, 2026, 8:31 p.m.
Created at: April 10, 2026, 4:48 a.m.