Triple
T8021990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potohari Punjabi |
E186759
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Pothwari Punjabi |
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 Punjabi | Statement: [Potohari Punjabi, hasAlternativeName, Pothwari Punjabi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pothwari Punjabi Context triple: [Potohari Punjabi, hasAlternativeName, Pothwari Punjabi]
-
A.
Potohari Punjabi
Potohari Punjabi is a regional variety of the Punjabi language spoken primarily in Pakistan’s Potohar Plateau and surrounding northern Punjab areas.
-
B.
Malwai Punjabi
Malwai Punjabi is a regional variety of the Punjabi language spoken primarily in the Malwa region of the Indian state of Punjab.
-
C.
Doabi Punjabi
Doabi Punjabi is a regional variety of the Punjabi language spoken primarily in the Doaba region of the Indian state of Punjab.
-
D.
Saraiki
Saraiki is an Indo-Aryan language spoken primarily in central and southern Pakistan, especially in the southern Punjab region.
-
E.
Pothwari
chosen
Pothwari is an Indo-Aryan language spoken primarily in Pakistan’s Potohar Plateau and surrounding regions, closely related to Punjabi and Hindko.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3e8eab9c81908098e6b17957316c |
completed | March 31, 2026, 3:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc63c6a9208190841ed55b8c6ec73f |
completed | April 1, 2026, 12:16 a.m. |
Created at: March 30, 2026, 5:20 p.m.