Triple
T5511369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jhelum, Pakistan |
E144571
|
entity |
| Predicate | localDialect |
P1762
|
FINISHED |
| Object | Pothwari |
E198841
|
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: Pothwari | Statement: [Jhelum, Pakistan, localDialect, Pothwari]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pothwari Context triple: [Jhelum, Pakistan, localDialect, Pothwari]
-
A.
Pothwari
chosen
Pothwari is an Indo-Aryan language spoken primarily in Pakistan’s Potohar Plateau and surrounding regions, closely related to Punjabi and Hindko.
-
B.
Pothohari
Pothohari is a dialect of Punjabi spoken primarily in the Pothohar Plateau region of northern Pakistan.
-
C.
Multani
Multani is a major dialect of the Saraiki language spoken primarily in the Multan region of Pakistan.
-
D.
Ganeriwala
Ganeriwala is an archaeological site associated with the ancient Indus Valley Civilization, located in present-day Pakistan.
-
E.
Gojal
Gojal is a high-altitude region in northern Pakistan’s Gilgit-Baltistan, known for its dramatic Karakoram mountain landscapes, glacial lakes, and Wakhi-speaking 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_69c008f6b5048190a09064116062cf69 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f4cbc2c819091fcbff5f39ceeb4 |
completed | March 22, 2026, 4:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c027cd14748190bd48d350cfe63603 |
completed | March 22, 2026, 5:33 p.m. |
Created at: March 22, 2026, 3:33 p.m.