Triple

T12058532
Position Surface form Disambiguated ID Type / Status
Subject Parachinar E287104 entity
Predicate dominantTribe P58898 FINISHED
Object Turi tribe E858685 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: Turi tribe | Statement: [Parachinar, dominantTribe, Turi tribe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Turi tribe
Context triple: [Parachinar, dominantTribe, Turi tribe]
  • A. Turi tribe chosen
    The Turi tribe is a prominent Pashtun Shia community primarily inhabiting the Kurram region along the Pakistan–Afghanistan border.
  • B. Ysty tribe
    The Ysty tribe is a constituent clan of the Senior zhuz, one of the traditional tribal confederations of the Kazakh people.
  • C. Korku tribe
    The Korku tribe is an indigenous Adivasi community of central India, primarily inhabiting forested regions of Madhya Pradesh and Maharashtra and known for its distinct Korku language and traditional agrarian lifestyle.
  • D. Jeturite tribe
    The Jeturite tribe was an ancient Arabian people mentioned in biblical genealogies, traditionally linked to the descendants of Ishmael.
  • E. Uysun tribe
    The Uysun tribe is a historical Kazakh tribal group traditionally associated with the Senior zhuz confederation in southern Kazakhstan.
  • 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_69d6ab4780948190bdb9f7620c2ac27e completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d9043dbccc8190bf9da181f826f0d8 completed April 10, 2026, 2:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69f49df216bc8190933e08f495f4d22f completed May 1, 2026, 12:34 p.m.
Created at: April 8, 2026, 9:47 p.m.