Triple

T618007
Position Surface form Disambiguated ID Type / Status
Subject British Sind E14447 entity
Predicate majorPort P528 FINISHED
Object Karachi Port E76591 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: Karachi Port | Statement: [British Sind, majorPort, Karachi Port]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Karachi Port
Context triple: [British Sind, majorPort, Karachi Port]
  • A. Port of Karachi chosen
    The Port of Karachi is Pakistan’s largest and busiest seaport, serving as a major hub for the country’s international trade and maritime activity.
  • B. Port Qasim
    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.
  • C. Kandla Port
    Kandla Port is a major commercial seaport on the western coast of India, serving as one of the country’s key hubs for maritime trade and cargo handling.
  • D. Pipavav Port
    Pipavav Port is a major private deep-water port on India’s western coast, serving as an important hub for container, bulk, and liquid cargo trade.
  • E. Mundra Port
    Mundra Port is India’s largest commercial port and a major deep-draft, all-weather cargo hub located on the Arabian Sea coast in the state of Gujarat.
  • 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_69a4934b17c881909ace8270e8ddd202 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a49e2418c881908552d2c4a5006e97 completed March 1, 2026, 8:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69a55a77b6648190a2d07471442b401a completed March 2, 2026, 9:37 a.m.
Created at: March 1, 2026, 7:35 p.m.