Triple
T15942569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lahndi |
E386601
|
entity |
| Predicate | hasDialect |
P4251
|
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: [Lahndi, hasDialect, Pothohari]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pothohari Context triple: [Lahndi, hasDialect, 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.
Jhalrapatan
Jhalrapatan is a historic town in Rajasthan, India, known for its ancient temples and role as an important cultural and religious center in the region.
-
D.
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.
-
E.
Kandhkot
Kandhkot is a town in Pakistan’s Sindh province that serves as a key urban and commercial center in the Kashmore District.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e156cefe948190af40eac92983edbc |
completed | April 16, 2026, 9:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb5bbc07c819098fd768e2e6b5b3e |
completed | May 9, 2026, 10:31 p.m. |
Created at: April 10, 2026, 4:53 a.m.