Triple

T22926466
Position Surface form Disambiguated ID Type / Status
Subject Khadan E569320 entity
Predicate royalLineage P9023 FINISHED
Object Borjigin family NE NERFINISHED

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: Borjigin family | Statement: [Khadan, royalLineage, Borjigin family]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Borjigin family
Context triple: [Khadan, royalLineage, Borjigin family]
  • A. Borjigin clan chosen
    The Borjigin clan was the royal Mongol lineage from which Genghis Khan and his descendants emerged, forming the ruling house of the Mongol Empire.
  • B. Mongol imperial family
    The Mongol imperial family was the ruling dynasty descended from Genghis Khan that governed the Mongol Empire and its successor states across Eurasia.
  • C. Khön family
    The Khön family is a hereditary Tibetan noble lineage that has traditionally provided the principal leaders of the Sakya school of Tibetan Buddhism.
  • D. Ögedeid lineage
    The Ögedeid lineage refers to the branch of Genghis Khan’s descendants stemming from his son Ögedei, which held the Great Khanate in the early Mongol Empire.
  • E. Harinxma family
    The Harinxma family is a historic noble lineage from Friesland in the Netherlands, influential in regional politics and landownership.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e2458f7d008190901dccbaebeaba24 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f180d90a9481908ea10019980b3951 completed April 29, 2026, 3:54 a.m.
Created at: April 17, 2026, 3:43 p.m.