Triple

T38283312
Position Surface form Disambiguated ID Type / Status
Subject research vessel Belafonte E1022133 entity
Predicate hasSubvessel P26083 FINISHED
Object submarine Deep Search 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: submarine Deep Search | Statement: [research vessel Belafonte, hasSubvessel, submarine Deep Search]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSubvessel
Context triple: [research vessel Belafonte, hasSubvessel, submarine Deep Search]
  • A. hasVessel chosen
    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. isVesselFor
    Indicates that one entity functions as a container or medium specifically used to hold, carry, or convey another entity.
  • C. hasVesselType
    Indicates that an entity is associated with or classified by a specific type of vessel (e.g., ship, boat, or container).
  • D. isSubsidiaryVentOf
    Indicates that one volcanic vent functions as a secondary or subordinate outlet associated with a primary or main vent.
  • E. usesVesselType
    Indicates that an entity performs an activity or operation by employing a specific type or category of vessel.
  • 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_69f76df0cddc81908d16c1556ff4097f completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_6a007fc9d9688190af411d5841af34be completed May 10, 2026, 12:53 p.m.
PD Predicate disambiguation batch_6a007f64813081909a2950336402073b completed May 10, 2026, 12:51 p.m.
Created at: May 3, 2026, 4:30 p.m.