Triple

T3004995
Position Surface form Disambiguated ID Type / Status
Subject Shina E81878 entity
Predicate closelyRelatedTo P37 FINISHED
Object Khowar E86212 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: Khowar | Statement: [Shina, closelyRelatedTo, Khowar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Khowar
Context triple: [Shina, closelyRelatedTo, Khowar]
  • A. Khowar chosen
    Khowar is an Indo-Aryan language primarily spoken in the Chitral region of Pakistan and parts of neighboring areas, known for its rich oral tradition and distinct phonology.
  • B. Brahui
    Brahui is a Dravidian language spoken primarily by the Brahui people in parts of Pakistan, Afghanistan, and Iran.
  • C. Kalasha language
    The Kalasha language is an endangered Indo-Aryan language spoken by the Kalash people in the remote valleys of Chitral District in northern Pakistan.
  • D. Gorani
    Gorani is a Northwestern Iranian language variety traditionally spoken by Kurdish communities in parts of Iran and Iraq, notable for its rich literary and religious heritage.
  • E. Saraiki
    Saraiki is an Indo-Aryan language spoken primarily in central and southern Pakistan, especially in the southern Punjab region.
  • 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_69ad8b1c4de88190a83b7cefaa1f2842 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad9a15ad9c81908255003bdb38d603 completed March 8, 2026, 3:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69b20f3d2fc481908365a171d8dac0df completed March 12, 2026, 12:56 a.m.
Created at: March 8, 2026, 2:59 p.m.