Triple

T30823110
Position Surface form Disambiguated ID Type / Status
Subject Lower Snake River Project E784981 entity
Predicate navigationInfrastructure P143540 FINISHED
Object navigation locks 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: navigation locks | Statement: [Lower Snake River Project, navigationInfrastructure, navigation locks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: navigationInfrastructure
Context triple: [Lower Snake River Project, navigationInfrastructure, navigation locks]
  • A. roadSystem
    Indicates a relationship where multiple roads are organized and connected as part of a larger, integrated transportation network or infrastructure.
  • B. transportNetwork
    Indicates a relationship where infrastructure or services enable the movement of people or goods between different locations.
  • C. transportInfrastructureFeature chosen
    Indicates a relationship where an entity is a specific element or component of transport infrastructure, such as roads, railways, or related facilities.
  • D. shareTransportInfrastructure
    Indicates that multiple entities make joint use of the same transport infrastructure facilities or systems.
  • E. trailInfrastructure
    Indicates that there is built or maintained infrastructure (such as paths, signage, or facilities) supporting the use or access of a trail between the related entities.
  • 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_69f224b6642481909e8d701de2cd1a53 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f690f3d1dc8190bba161d92fd2065d completed May 3, 2026, 12:04 a.m.
PD Predicate disambiguation batch_69f68b7d2794819092fef8a63f4f3de8 completed May 2, 2026, 11:40 p.m.
Created at: April 29, 2026, 8:44 p.m.