Triple
T6921822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khairpur |
E160202
|
entity |
| Predicate | hasTitle |
P38
|
FINISHED |
| Object | Khairpur Mirs |
E160202
|
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: Khairpur Mirs | Statement: [Khairpur, hasTitle, Khairpur Mirs]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Khairpur Mirs Context triple: [Khairpur, hasTitle, Khairpur Mirs]
-
A.
Nawabshah
Nawabshah is a major city in Pakistan known as an important commercial and agricultural center in the Sindh province.
-
B.
Narowal
Narowal is a city in the Punjab province of Pakistan, located close to the border with India and known for its agricultural surroundings and proximity to the Ravi River.
-
C.
Shikarpur
Shikarpur is a historic city in the Sindh province of Pakistan, known for its old trading heritage and distinctive cultural and architectural traditions.
-
D.
Khairpur
chosen
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.
Khanewal
Khanewal is a prominent city in Pakistan’s Punjab province, known as an important railway junction and agricultural trade center.
- 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_69c6884d350081908d8a970e4d40ad78 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9fb8ac48190b50bbc47fad8288f |
completed | March 27, 2026, 7:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c75137dd848190b35ff72725f886ba |
completed | March 28, 2026, 3:55 a.m. |
Created at: March 27, 2026, 2:26 p.m.