Triple

T23166343
Position Surface form Disambiguated ID Type / Status
Subject Mongol imperial family E578720 entity
Predicate hasMember P10 FINISHED
Object Berke 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: Berke | Statement: [Mongol imperial family, hasMember, Berke]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Berke
Context triple: [Mongol imperial family, hasMember, Berke]
  • A. Berke
    Berke is a surname most notably associated with Deborah Berke, an American architect and academic leader.
  • B. Berke
    Berke is an alternate name for Dovber Schneuri, the second rebbe of the Chabad-Lubavitch Hasidic movement and a prominent early 19th-century Jewish spiritual leader.
  • C. Khan of the Golden Horde chosen
    The Khan of the Golden Horde was the supreme ruler of the western Mongol khanate that dominated much of Eastern Europe and parts of Russia from the 13th to the 15th century.
  • D. Qara Hülegü
    Qara Hülegü was a 13th-century Mongol prince of the Chagatai lineage who briefly ruled the Chagatai Khanate during the early period of the Mongol Empire.
  • E. Tokhtamysh
    Tokhtamysh was a late 14th-century khan of the Golden Horde who briefly reunited its territories and clashed with the Central Asian conqueror Timur.
  • 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.