Triple
T7753897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sibi District |
E175840
|
entity |
| Predicate | languageSpoken |
P151
|
FINISHED |
| Object | Saraiki |
E14560
|
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: Saraiki | Statement: [Sibi District, languageSpoken, Saraiki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Saraiki Context triple: [Sibi District, languageSpoken, Saraiki]
-
A.
Saraiki
chosen
Saraiki is an Indo-Aryan language spoken primarily in central and southern Pakistan, especially in the southern Punjab region.
-
B.
Khowar
Khowar is an Indo-Aryan language primarily spoken in the Chitral region of Pakistan and parts of neighboring areas, known for its rich oral tradition and distinct phonology.
-
C.
Mirpuri
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.
-
D.
Sindhi
Sindhi is an Indo-Aryan language spoken primarily in Pakistan and India, known for its rich literary tradition and distinct script variants.
-
E.
Dogri
Dogri is an Indo-Aryan language spoken primarily in the Jammu region of India and surrounding areas, recognized as one of the official languages of India.
- 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_69c6996180088190832e38e8d83ff54a |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c703d851d4819091e9117d3f34cb9a |
completed | March 27, 2026, 10:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8be5a649c81909c94d629348b34fc |
completed | March 29, 2026, 5:53 a.m. |
Created at: March 27, 2026, 4:08 p.m.