Triple

T18438073
Position Surface form Disambiguated ID Type / Status
Subject Korangi Creek E450446 entity
Predicate near P350 FINISHED
Object Port Qasim 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: Port Qasim | Statement: [Korangi Creek, near, Port Qasim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Port Qasim
Context triple: [Korangi Creek, near, Port Qasim]
  • A. Port Qasim chosen
    Port Qasim is Pakistan’s second-busiest deep-sea commercial port and a major industrial and shipping hub located near Karachi on the Arabian Sea.
  • B. Navlakhi Port
    Navlakhi Port is a minor commercial seaport in Gujarat, India, serving as a regional hub for handling bulk cargo along the Gulf of Kutch.
  • C. Adabiya Port
    Adabiya Port is a commercial seaport on Egypt’s Red Sea coast that serves as a key hub for handling general cargo and bulk goods.
  • D. Kalabahi Port
    Kalabahi Port is the main seaport and maritime gateway serving the island and regency of Alor in East Nusa Tenggara, Indonesia.
  • E. Al Maqal Port
    Al Maqal Port is a historic river port in the city of Basra in southern Iraq, serving as an important hub for regional trade and shipping along the Shatt al-Arab waterway.
  • 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.