Triple
T3696882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kot Diji |
E78478
|
entity |
| Predicate | nearbyCity |
P350
|
FINISHED |
| Object | Sukkur |
E77817
|
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: Sukkur | Statement: [Kot Diji, nearbyCity, Sukkur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sukkur Context triple: [Kot Diji, nearbyCity, Sukkur]
-
A.
Sukkur
chosen
Sukkur is a major city in Pakistan known for its strategic location on the Indus River and its role as an important commercial and cultural center in northern Sindh.
-
B.
Multan
Multan is a historic city in southern Punjab, Pakistan, renowned as a major cultural, commercial, and Sufi spiritual center with a legacy spanning over two millennia.
-
C.
Rahim Yar Khan
Rahim Yar Khan is a major city in southern Punjab, Pakistan, known as an important commercial and agricultural center in the Seraiki-speaking region.
-
D.
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.
-
E.
Haripur
Haripur is a city in northern Pakistan known as an administrative and commercial center in the Hazara region of Khyber Pakhtunkhwa.
- 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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc5115ad8819085ffa938de3943f4 |
completed | March 8, 2026, 6:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5d03dbd348190aaaa58a352982248 |
completed | March 14, 2026, 9:16 p.m. |
Created at: March 8, 2026, 3:26 p.m.