Triple
T16033166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | western Punjab region |
E388898
|
entity |
| Predicate | hasDialect |
P4251
|
FINISHED |
| Object | Multani (Saraiki) |
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 (Saraiki) | Statement: [western Punjab region, hasDialect, Multani (Saraiki)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Multani (Saraiki) Context triple: [western Punjab region, hasDialect, Multani (Saraiki)]
-
A.
Saraiki
Saraiki is an Indo-Aryan language spoken primarily in central and southern Pakistan, especially in the southern Punjab region.
-
B.
Abbottabadi Hindko
Abbottabadi Hindko is a regional variety of the Hindko language spoken primarily in and around the city of Abbottabad in northern Pakistan.
-
C.
Peshawari Hindko
Peshawari Hindko is a regional variety of the Hindko language spoken primarily in and around the city of Peshawar in Pakistan.
-
D.
Multani
chosen
Multani is a major dialect of the Saraiki language spoken primarily in the Multan region of Pakistan.
-
E.
Sindhi Khudabadi
Sindhi Khudabadi is a historical script used primarily by Sindhi-speaking merchant communities for writing the Sindhi language, especially in commercial and administrative contexts.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e183396a708190b53a589f6ac2c5bc |
completed | April 17, 2026, 12:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffcf373f548190abfc93aa238b97fd |
completed | May 10, 2026, 12:20 a.m. |
Created at: April 10, 2026, 4:56 a.m.