Triple

T7212998
Position Surface form Disambiguated ID Type / Status
Subject Nomukhan E149454 entity
Predicate grandfather P979 FINISHED
Object Tolui E136173 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: Tolui | Statement: [Nomukhan, grandfather, Tolui]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tolui
Context triple: [Nomukhan, grandfather, Tolui]
  • A. Tolui chosen
    Tolui was a prominent Mongol general and the fourth son of Genghis Khan, known for his key role in expanding and consolidating the Mongol Empire.
  • B. Satank
    Satank was a prominent 19th-century Kiowa war leader and medicine man known for his resistance to U.S. expansion onto Native American lands.
  • C. Subutai
    Subutai was a brilliant 13th-century Mongol general and primary strategist of Genghis Khan and Ögedei Khan, renowned for his far-ranging campaigns and innovative military tactics across Asia and Europe.
  • D. Taimuri Aimaqs
    Taimuri Aimaqs are a distinct tribal subgroup of the Aimaq people, traditionally semi-nomadic and primarily inhabiting parts of western and central Afghanistan.
  • E. Jochi
    Jochi was the eldest son of Genghis Khan and a Mongol prince whose disputed legitimacy influenced the succession politics of the early Mongol Empire.
  • 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_69c687eca814819095abb52316b1af80 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6e98b61448190add3624a818fdc7b completed March 27, 2026, 8:33 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7bfcec3448190ab29c3742aa167ae completed March 28, 2026, 11:47 a.m.
Created at: March 27, 2026, 2:53 p.m.