Triple
T8420652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindko |
E198840
|
entity |
| Predicate | hasDialect |
P4251
|
FINISHED |
| Object | Mirpuri Hindko |
E386604
|
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: Mirpuri Hindko | Statement: [Hindko, hasDialect, Mirpuri Hindko]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mirpuri Hindko Context triple: [Hindko, hasDialect, Mirpuri Hindko]
-
A.
Mirpuri
chosen
Mirpuri is a major dialect of the Lahnda (Western Punjabi) language, primarily spoken in the Mirpur region of Azad Kashmir and among its diaspora communities.
-
B.
Garhwali
Garhwali is an Indo-Aryan language spoken primarily in the Garhwal region of the Indian state of Uttarakhand.
-
C.
Hindko
Hindko is a group of Indo-Aryan dialects spoken primarily in northern Pakistan, especially in parts of Khyber Pakhtunkhwa and Azad Kashmir.
-
D.
Bhojpuri
Bhojpuri is an Indo-Aryan language spoken primarily in eastern Uttar Pradesh, western Bihar, and parts of Nepal, with a rich folk culture and a large diaspora community.
-
E.
Nagpuri
Nagpuri is an Indo-Aryan language spoken primarily in parts of eastern India, especially in and around the present-day state of Jharkhand.
- 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_69ca8312d63c8190bf133b676b44a385 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb84ca7b348190abab25e79b05407f |
completed | March 31, 2026, 8:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce03476b288190b3df8f9f4d502ea8 |
completed | April 2, 2026, 5:48 a.m. |
Created at: March 30, 2026, 6:06 p.m.