Triple

T13303747
Position Surface form Disambiguated ID Type / Status
Subject Vengurla E316878 entity
Predicate hasPort P35 FINISHED
Object Vengurla port E313114 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: Vengurla port | Statement: [Vengurla, hasPort, Vengurla port]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vengurla port
Context triple: [Vengurla, hasPort, Vengurla port]
  • A. 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.
  • B. 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.
  • C. Cambay port
    Cambay port is a historic maritime trading hub on the western coast of India in Gujarat, long known for its role in regional and international commerce.
  • D. Ratnagiri port chosen
    Ratnagiri port is a coastal maritime facility in Maharashtra, India, serving as a regional hub for fishing, coastal trade, and limited cargo operations along the Konkan coast.
  • E. Kamarajar Port
    Kamarajar Port is a major deep-water seaport near Chennai on India’s east coast, serving as a key hub for cargo and industrial maritime trade.
  • 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_69d806b40ab4819094adf6c374f4811a completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d990a60eb08190bf0dc098ca7dc342 completed April 11, 2026, 12:07 a.m.
NED1 Entity disambiguation (via context triple) batch_69f71f262fd88190ba8871f8761a660b completed May 3, 2026, 10:10 a.m.
Created at: April 9, 2026, 9:28 p.m.