Triple

T15672584
Position Surface form Disambiguated ID Type / Status
Subject Kashmore E377351 entity
Predicate languageUsed P238 FINISHED
Object Saraiki E14560 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: Saraiki | Statement: [Kashmore, languageUsed, Saraiki]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Saraiki
Context triple: [Kashmore, languageUsed, Saraiki]
  • A. Saraiki chosen
    Saraiki is an Indo-Aryan language spoken primarily in central and southern Pakistan, especially in the southern Punjab region.
  • B. Abbottabadi Hindko
    Abbottabadi Hindko is a regional variety of the Hindko language spoken primarily in and around the city of Abbottabad in northern Pakistan.
  • C. Peshawari Hindko
    Peshawari Hindko is a regional variety of the Hindko language spoken primarily in and around the city of Peshawar in Pakistan.
  • D. Pahari-Pothwari
    Pahari-Pothwari is an Indo-Aryan language variety spoken primarily in the Pothohar Plateau of northern Pakistan and adjoining regions, often considered transitional between Punjabi and Hindko.
  • E. Khowar
    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.
  • 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_69d85cd2e28481909d4e975bee20872f completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04f13b1b08190beabc9f4098aa096 completed April 16, 2026, 2:53 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff6edb12bc8190b2c5558190671ae5 completed May 9, 2026, 5:28 p.m.
Created at: April 10, 2026, 4:16 a.m.