Triple

T8420710
Position Surface form Disambiguated ID Type / Status
Subject Pothwari E198841 entity
Predicate alternativeName P39 FINISHED
Object Pothohari E201721 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: Pothohari | Statement: [Pothwari, alternativeName, Pothohari]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pothohari
Context triple: [Pothwari, alternativeName, Pothohari]
  • A. Pothohari chosen
    Pothohari is a dialect of Punjabi spoken primarily in the Pothohar Plateau region of northern Pakistan.
  • B. Saida Khera
    Saida Khera is a village in Punjab, India, known in folklore as a setting linked to the legendary love story of Heer Ranjha.
  • C. Lehri
    Lehri is a town and administrative area in Pakistan’s Balochistan province, known for its rural character and role as a local hub within the region.
  • D. Ghotki
    Ghotki is a city in Pakistan’s Sindh province known for its agricultural economy and proximity to major gas fields and industrial installations.
  • E. Khaplu
    Khaplu is a historic town in northern Pakistan’s Gilgit-Baltistan region, known as a gateway to the Karakoram mountains and for its traditional Balti culture and architecture.
  • 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_69ca8312d63c8190bf133b676b44a385 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cb84ca7b348190abab25e79b05407f completed March 31, 2026, 8:24 a.m.
NED1 Entity disambiguation (via context triple) batch_69ce4db8bd5481909bb41053832f60ba completed April 2, 2026, 11:06 a.m.
Created at: March 30, 2026, 6:06 p.m.