Triple

T7015534
Position Surface form Disambiguated ID Type / Status
Subject Haldia Port E162690 entity
Predicate connectedTo P37 FINISHED
Object Kolkata Port E222641 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: Kolkata Port | Statement: [Haldia Port, connectedTo, Kolkata Port]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kolkata Port
Context triple: [Haldia Port, connectedTo, Kolkata Port]
  • A. Mormugao Port
    Mormugao Port is a major natural harbor and one of India’s leading iron ore exporting ports, located in the state of Goa on the Arabian Sea.
  • B. Paradip Port
    Paradip Port is a major deep-water seaport on the east coast of India that serves as a key hub for maritime trade and cargo handling in the Bay of Bengal region.
  • C. Indoji Port
    Indoji Port is a harbor facility located on Iki Island in Japan, serving as one of the island’s key maritime access points.
  • D. Kolkata Port Trust chosen
    Kolkata Port Trust is the statutory authority that manages and operates the major riverine port facilities and related infrastructure in Kolkata, India.
  • E. Cochin Port
    Cochin Port is a major Indian seaport on the Arabian Sea, serving as a key maritime trade and container hub for the state of Kerala.
  • 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_69c6885a127c8190867b059bdccf13ff completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6e1d43e948190843f1cef3ce2004e completed March 27, 2026, 8 p.m.
NED1 Entity disambiguation (via context triple) batch_69c79c7e87b88190bed99f68bbffa186 completed March 28, 2026, 9:16 a.m.
Created at: March 27, 2026, 2:34 p.m.