Triple
T1890717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seraiki |
E41867
|
entity |
| Predicate | hasDialects |
P4251
|
FINISHED |
| Object | Multani |
E77870
|
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: Multani | Statement: [Seraiki, hasDialects, Multani]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Multani Context triple: [Seraiki, hasDialects, Multani]
-
A.
Multani
chosen
Multani is a major dialect of the Saraiki language spoken primarily in the Multan region of Pakistan.
-
B.
Pothwari
Pothwari is an Indo-Aryan language spoken primarily in Pakistan’s Potohar Plateau and surrounding regions, closely related to Punjabi and Hindko.
-
C.
Pothohari
Pothohari is a dialect of Punjabi spoken primarily in the Pothohar Plateau region of northern Pakistan.
-
D.
Bagri
Bagri is an Indo-Aryan language variety spoken primarily in parts of Rajasthan, Haryana, and Punjab, often considered a dialect of Rajasthani.
-
E.
Sher-e-Punjab
Sher-e-Punjab is the honorific title of Maharaja Ranjit Singh, the famed 19th-century Sikh ruler who unified much of the Punjab region into a powerful empire.
- 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_69a8864b6de0819098d089f6a1b910a7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb14475448190b291ada3454bf98b |
completed | March 7, 2026, 5:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69addf68a8d48190a3360557def67692 |
completed | March 8, 2026, 8:43 p.m. |
Created at: March 4, 2026, 7:34 p.m.