Triple
T19608399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palampur |
E470664
|
entity |
| Predicate | regionalLanguage |
P237
|
FINISHED |
| Object | Pahari |
—
|
NE NERFINISHED |
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: Pahari | Statement: [Palampur, regionalLanguage, Pahari]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pahari Context triple: [Palampur, regionalLanguage, Pahari]
-
A.
Pahari
Pahari is a town located in India’s culturally significant Braj region, known for its association with Hindu religious traditions and heritage.
-
B.
Pahari
chosen
Pahari is an Indo-Aryan language spoken by communities in the Jammu region of northern India, closely related to other Western Pahari dialects of the Himalayas.
-
C.
Chamba Pahari
Chamba Pahari is an Indo-Aryan language variety spoken in and around the Chamba region of Himachal Pradesh in northern India.
-
D.
Pahari-Potohari
Pahari-Potohari is an Indo-Aryan language variety spoken primarily in the Potohar Plateau and surrounding regions of northern Pakistan, often considered a transitional form between Punjabi and Hindko.
-
E.
Kullu Pahari
Kullu Pahari is an Indo-Aryan language spoken primarily in the Kullu Valley of Himachal Pradesh in northern India.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640c964fc8190bd1cb60f4b233eaa |
completed | April 20, 2026, 3:05 p.m. |
Created at: April 10, 2026, 1:43 p.m.