Triple

T21749413
Position Surface form Disambiguated ID Type / Status
Subject Mirpur District E536872 entity
Predicate majorLanguage P207 FINISHED
Object Pahari-Pothwari 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: Pahari-Pothwari | Statement: [Mirpur District, majorLanguage, Pahari-Pothwari]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pahari-Pothwari
Context triple: [Mirpur District, majorLanguage, Pahari-Pothwari]
  • A. Pahari-Pothwari chosen
    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.
  • B. Peshawari Hindko
    Peshawari Hindko is a regional variety of the Hindko language spoken primarily in and around the city of Peshawar in Pakistan.
  • C. Saraiki
    Saraiki is an Indo-Aryan language spoken primarily in central and southern Pakistan, especially in the southern Punjab region.
  • D. Dogri
    Dogri is an Indo-Aryan language spoken primarily in the Jammu region of India and surrounding areas, recognized as one of the official languages of India.
  • E. Garhwali
    Garhwali is an Indo-Aryan language spoken primarily in the Garhwal region of the Indian state of Uttarakhand.
  • 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_69e0c46eab808190b848242d63a17c47 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f01a78bd908190b74e26ab1cc8788f completed April 28, 2026, 2:24 a.m.
Created at: April 16, 2026, 6:50 p.m.