Triple
T16608329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multan Mint |
E403501
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Multan |
E90805
|
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: Multan | Statement: [Multan Mint, locatedIn, Multan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Multan Context triple: [Multan Mint, locatedIn, Multan]
-
A.
Multan
chosen
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.
-
B.
Faisalabad
Faisalabad is a major industrial city in Pakistan’s Punjab province, known especially for its large textile industry and role as a commercial hub.
-
C.
Sukkur
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.
-
D.
Bahawalnagar
Bahawalnagar is a prominent city in Pakistan’s Punjab province, known as an agricultural and commercial hub near the border with India.
-
E.
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.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e36093901881909b85af47f75879a9 |
completed | April 18, 2026, 10:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0179313470819090351e937ea34701 |
completed | May 11, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:17 a.m.