Triple

T34213094
Position Surface form Disambiguated ID Type / Status
Subject St. Peters Canal E877711 entity
Predicate allowsVesselPassageBetween P169924 FINISHED
Object Atlantic Ocean 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: Atlantic Ocean | Statement: [St. Peters Canal, allowsVesselPassageBetween, Atlantic Ocean]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: allowsVesselPassageBetween
Context triple: [St. Peters Canal, allowsVesselPassageBetween, Atlantic Ocean]
  • A. supportsBargeTrafficTo
    Indicates that one entity enables or facilitates barge traffic or navigation to another entity.
  • B. isVesselFor
    Indicates that one entity functions as a container or medium specifically used to hold, carry, or convey another entity.
  • C. hasFishPassage
    Indicates that there exists a structure or feature that allows fish to move or migrate through, past, or around a barrier such as a dam or weir.
  • D. allowsCanalTraffic chosen
    Indicates that something permits or enables the passage of vessels or waterborne transport through a canal.
  • E. 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.
  • 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_69f349b0b4bc819088c1552424089ee9 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69fd09840ea88190a2e6d7e577ade717 completed May 7, 2026, 9:52 p.m.
PD Predicate disambiguation batch_69fd064c49988190afadddbd04d7cb94 completed May 7, 2026, 9:38 p.m.
Created at: May 1, 2026, 1:55 a.m.