Triple
T2423739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haripur |
E53477
|
entity |
| Predicate | languageSpoken |
P151
|
FINISHED |
| Object | Hindko |
E198840
|
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: Hindko | Statement: [Haripur, languageSpoken, Hindko]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hindko Context triple: [Haripur, languageSpoken, Hindko]
-
A.
Hindko
chosen
Hindko is a group of Indo-Aryan dialects spoken primarily in northern Pakistan, especially in parts of Khyber Pakhtunkhwa and Azad Kashmir.
-
B.
Sant Bhasha
Sant Bhasha is a historical North Indian devotional literary language used in Sikh and related spiritual poetry, written in the Gurmukhi script.
-
C.
Kurukh
Kurukh is an indigenous Dravidian language spoken primarily by the Oraon tribal communities in eastern and central India.
-
D.
Bagheli
Bagheli is an Indo-Aryan language spoken primarily in the Bagelkhand region of central India, closely related to Hindi and used by millions as a regional vernacular.
-
E.
Awadhi
Awadhi is an Indo-Aryan language of northern India, traditionally spoken in parts of Uttar Pradesh and surrounding regions and known for its rich literary and folk traditions.
- 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_69ab495c44d48190b7235b23719bc3f6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc973aee08190b543492f436f3fe5 |
completed | March 7, 2026, 6:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69aebf5e33208190a6899e6672b3daeb |
completed | March 9, 2026, 12:38 p.m. |
Created at: March 6, 2026, 9:42 p.m.