Triple

T28645238
Position Surface form Disambiguated ID Type / Status
Subject Pier 86 E725033 entity
Predicate hasDockedVessel P14974 FINISHED
Object USS Intrepid (CV-11) 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: USS Intrepid (CV-11) | Statement: [Pier 86, hasDockedVessel, USS Intrepid (CV-11)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDockedVessel
Context triple: [Pier 86, hasDockedVessel, USS Intrepid (CV-11)]
  • A. hasVessel
    Indicates that one entity possesses, uses, or is associated with a particular vessel (such as a container, ship, or transport medium) in the context of the described relationship or action.
  • B. hasDryDock
    Indicates that one entity possesses, contains, or is equipped with a dry dock facility used for servicing or repairing vessels out of the water.
  • C. berthingOrDockingTarget chosen
    Indicates that an entity serves as the location or structure where a vessel or vehicle is intended to berth or dock.
  • D. namedVesselOf
    Indicates that one entity is the specific named vessel (e.g., ship, boat, or craft) associated with or belonging to another entity.
  • E. mooredAt
    Indicates that one object, typically a vessel or floating structure, is secured or anchored at a specific location or facility.
  • 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_69f01d8423888190bd2f4e52605bf261 completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_69f68f670b608190a0b6ab60d722b4e0 completed May 2, 2026, 11:57 p.m.
PD Predicate disambiguation batch_69f68b78f29481908cc8f390496dee97 completed May 2, 2026, 11:40 p.m.
Created at: April 28, 2026, 4:47 a.m.