Triple

T19298988
Position Surface form Disambiguated ID Type / Status
Subject Port of New Orleans E482643 entity
Predicate isOceanAccessPort P12922 FINISHED
Object true LITERAL 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: true | Statement: [Port of New Orleans, isOceanAccessPort, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isOceanAccessPort
Context triple: [Port of New Orleans, isOceanAccessPort, true]
  • A. isDeepWaterPort
    Indicates that a port has sufficiently deep water to accommodate large, heavily loaded vessels without grounding.
  • B. isInlandPort
    Indicates that a port facility is located inland, away from the open sea, typically on a river, canal, or lake, while still serving maritime or shipping functions.
  • C. isDeepwaterPortTerminus
    Indicates that a location serves as the endpoint or final stop of a transportation route at a deepwater port capable of accommodating large, ocean-going vessels.
  • D. isMainDeepWaterPortFor
    Indicates that one location serves as the primary deep-water port facility for another entity, such as a region, city, or country.
  • E. hasSeaAccess chosen
    Indicates that an entity has direct access to the sea, typically via a coastline, port, or navigable waterway connected to the sea.
  • F. None of above.

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_69d8e8d04d5c8190baa816986f2b1d1e completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e5fc8852208190ba0337a9623d9bdf completed April 20, 2026, 10:14 a.m.
PD Predicate disambiguation batch_69e4dd0bc7508190a6f9d56bd4c3404f completed April 19, 2026, 1:47 p.m.
Created at: April 10, 2026, 1:31 p.m.