Triple
T16510068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multan Division |
E401036
|
entity |
| Predicate | hasMajorCity |
P316
|
FINISHED |
| Object | Vehari |
E769817
|
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: Vehari | Statement: [Multan Division, hasMajorCity, Vehari]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vehari Context triple: [Multan Division, hasMajorCity, Vehari]
-
A.
Vehari
chosen
Vehari is a city in the Punjab province of Pakistan, known as an agricultural and educational hub in the region.
-
B.
Attock
Attock is a historic city in northern Pakistan strategically located along the Indus River, long serving as a key gateway between the Punjab region and Khyber Pakhtunkhwa.
-
C.
Bahawalnagar
Bahawalnagar is a prominent city in Pakistan’s Punjab province, known as an agricultural and commercial hub near the border with India.
-
D.
Khairpur
Khairpur is a historic city in Sindh, Pakistan, known for its former princely state status under the Talpur rulers and its rich cultural and architectural heritage.
-
E.
Bahawalpur
Bahawalpur is a historic city in southern Punjab, Pakistan, known for its former princely state status, grand palaces, and proximity to the Cholistan Desert.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e54f7508190804bbae4c9bc8fe3 |
completed | April 18, 2026, 7:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01481c3084819099e198c408bea464 |
completed | May 11, 2026, 3:08 a.m. |
Created at: April 10, 2026, 5:14 a.m.