Triple

T17972870
Position Surface form Disambiguated ID Type / Status
Subject Suleyman Shah E449390 entity
Predicate tribalAffiliation P13151 FINISHED
Object Kayı tribe 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: Kayı tribe | Statement: [Suleyman Shah, tribalAffiliation, Kayı tribe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kayı tribe
Context triple: [Suleyman Shah, tribalAffiliation, Kayı tribe]
  • A. Kayı tribe chosen
    The Kayı tribe was a prominent Oghuz Turkic clan traditionally regarded as the ancestral tribe of Osman I and the founding lineage of the Ottoman Empire.
  • B. Uysun tribe
    The Uysun tribe is a historical Kazakh tribal group traditionally associated with the Senior zhuz confederation in southern Kazakhstan.
  • C. Ysty tribe
    The Ysty tribe is a constituent clan of the Senior zhuz, one of the traditional tribal confederations of the Kazakh people.
  • D. Wea tribe
    The Wea tribe is a Native American people of the Algonquian language family historically associated with the Wabash River region in present-day Indiana and neighboring areas.
  • E. Jeturite tribe
    The Jeturite tribe was an ancient Arabian people mentioned in biblical genealogies, traditionally linked to the descendants of Ishmael.
  • 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_69d8b9f9927c8190a006110c8b996e61 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4b1fca04481908f0dd875953fd82f completed April 19, 2026, 10:44 a.m.
Created at: April 10, 2026, 10:22 a.m.