Triple
T18438074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korangi Creek |
E450446
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Bin Qasim Town |
—
|
NE NERFINISHED |
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: Bin Qasim Town | Statement: [Korangi Creek, near, Bin Qasim Town]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bin Qasim Town Context triple: [Korangi Creek, near, Bin Qasim Town]
-
A.
Bin Qasim Town
chosen
Bin Qasim Town is a residential and industrial locality in the eastern part of Karachi, Pakistan, known for its proximity to the Port Qasim industrial area.
-
B.
Saddar Town
Saddar Town is a central, densely populated urban area of Karachi known for its historic markets, colonial-era architecture, and major commercial and administrative centers.
-
C.
Haroonabad
Haroonabad is a town in Pakistan known for its agricultural surroundings and role as a local commercial center.
-
D.
Jauharabad
Jauharabad is a planned town in Pakistan’s Punjab province, known for its proximity to key industrial and strategic facilities.
-
E.
Akhthala town
Akhthala town is a historic settlement in northern Armenia known for its medieval monastery and scenic location amid the Debed Canyon.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51c0ed6708190ae90efd8455ec352 |
completed | April 19, 2026, 6:16 p.m. |
Created at: April 10, 2026, 11:29 a.m.