Triple

T29311684
Position Surface form Disambiguated ID Type / Status
Subject Pacific Ocean via Coos Bay E743249 entity
Predicate isNavigationApproachFor P84544 FINISHED
Object Port of Coos Bay 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 of Coos Bay | Statement: [Pacific Ocean via Coos Bay, isNavigationApproachFor, Port of Coos Bay]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isNavigationApproachFor
Context triple: [Pacific Ocean via Coos Bay, isNavigationApproachFor, Port of Coos Bay]
  • A. hasApproachHeading
    Indicates that an entity follows or is aligned with a specified heading or direction when making an approach.
  • B. hasInstrumentApproach
    Indicates that an approach procedure to a location or runway is conducted using specified navigation instruments or instrument-based methods.
  • C. hasApproachControl
    Indicates that one entity exercises approach control authority or responsibility over another entity, typically managing its approach phase or access.
  • D. hasApproachTrail
    Indicates that there is a designated trail or path providing access or approach to a particular location or feature.
  • E. hasNavigationPurpose chosen
    Indicates that something exists or is designed specifically to serve a navigational function or goal.
  • 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_69f0912502c8819087d9e8398ee991a8 completed April 28, 2026, 10:51 a.m.
NER Named-entity recognition batch_69f665e5ade481908eac1b24726ba5b5 completed May 2, 2026, 9 p.m.
PD Predicate disambiguation batch_69f660f2e3708190ab658652bcfc04d0 completed May 2, 2026, 8:39 p.m.
Created at: April 28, 2026, 1:17 p.m.