Triple
T8522268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pahari-Potohari |
E201720
|
entity |
| Predicate | hasDialect |
P4251
|
FINISHED |
| Object | Potohari |
E39207
|
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: Potohari | Statement: [Pahari-Potohari, hasDialect, Potohari]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Potohari Context triple: [Pahari-Potohari, hasDialect, Potohari]
-
A.
Potohari
chosen
Potohari is an Indo-Aryan language variety spoken in the Potohar Plateau region of northern Pakistan, including areas around Islamabad and Rawalpindi.
-
B.
Surkhob
Surkhob is the historical name of a major river in Central Asia that forms part of what is now known as the Vakhsh River in Tajikistan.
-
C.
Gogra
Gogra is an alternative name for Kauriala, a locality whose identity is primarily tied to this regional designation.
-
D.
Khaltahi
Khaltahi is a regional dialect of the Chhattisgarhi language spoken in parts of central India.
-
E.
Sairang
Sairang is a small town in the Indian state of Mizoram, known for its scenic riverside setting and role as a transport and trading hub near the state capital Aizawl.
- 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_69ca8321bb44819081b74df0b710276d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe64215408190b45f462a32d3471d |
completed | March 31, 2026, 3:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce4e8399f481909992aedf0d918cbc |
completed | April 2, 2026, 11:09 a.m. |
Created at: March 30, 2026, 6:16 p.m.