Triple

T9460719
Position Surface form Disambiguated ID Type / Status
Subject Yidgha E228136 entity
Predicate hasContactLanguage P8345 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: [Yidgha, hasContactLanguage, Khowar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Khowar
Context triple: [Yidgha, hasContactLanguage, 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. Mirpuri
    Mirpuri is a major dialect of the Lahnda (Western Punjabi) language, primarily spoken in the Mirpur region of Azad Kashmir and among its diaspora communities.
  • 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_69ca843b123881909b0e60028475d12d completed March 30, 2026, 2:10 p.m.
NER Named-entity recognition batch_69cd7fcaf610819092bcd3b871665aa5 completed April 1, 2026, 8:27 p.m.
NED1 Entity disambiguation (via context triple) batch_69d12ce01b548190a30f6cc7f3084b06 completed April 4, 2026, 3:23 p.m.
Created at: March 30, 2026, 7:52 p.m.