Triple

T23166355
Position Surface form Disambiguated ID Type / Status
Subject Mongol imperial family E578720 entity
Predicate hasMember P10 FINISHED
Object Jani Beg 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: Jani Beg | Statement: [Mongol imperial family, hasMember, Jani Beg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jani Beg
Context triple: [Mongol imperial family, hasMember, Jani Beg]
  • A. Jani Beg chosen
    Jani Beg was a 14th-century khan of the Golden Horde known for expanding its power and for his role in the decline of the unified Mongol Empire.
  • B. Berdi Beg
    Berdi Beg was a 14th-century ruler of the Golden Horde whose brief and turbulent reign contributed to the khanate’s political fragmentation and decline.
  • C. Safa Giray
    Safa Giray was a 16th-century khan of Kazan known for his resistance to Russian expansion and his turbulent, often interrupted reign.
  • D. Nogai
    Nogai is a Turkic language spoken primarily by the Nogai people of the North Caucasus region in Russia.
  • E. Bairam Beg
    Bairam Beg, better known as Bairam Khan, was a prominent 16th-century Turkic military commander and statesman who served as regent and chief advisor to the Mughal emperor Akbar.
  • 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_69e245fc75348190a0288401044c8af8 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18f2c923c81908b58811fffdcf932 completed April 29, 2026, 4:55 a.m.
Created at: April 17, 2026, 4:03 p.m.