Triple

T26799807
Position Surface form Disambiguated ID Type / Status
Subject Burleigh Falls E671065 entity
Predicate isNavigationFeature P47583 FINISHED
Object obstacle bypassed by lock 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: obstacle bypassed by lock | Statement: [Burleigh Falls, isNavigationFeature, obstacle bypassed by lock]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isNavigationFeature
Context triple: [Burleigh Falls, isNavigationFeature, obstacle bypassed by lock]
  • A. hasNavigationCharacteristic chosen
    Indicates that an entity possesses a specific property, feature, or quality related to navigation or navigational behavior.
  • B. isOnNavigation
    Indicates that one entity is currently located on, or actively using, a navigation interface, route, or control associated with another entity.
  • C. isNavigableVia
    Indicates that one entity can be reached, traversed, or accessed by means of another entity (such as a route, medium, or pathway).
  • D. isNavigationStar
    Indicates that one entity serves as a guiding or reference star used for navigation relative to another entity.
  • E. hasNavigationUse
    Indicates that something is used for navigation or serves a navigational function in relation to another entity.
  • 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_69eeb31fbd888190a82dac5822e453bc completed April 27, 2026, 12:51 a.m.
NER Named-entity recognition batch_69f619c4056c8190a7a4ce82858c6ed5 completed May 2, 2026, 3:35 p.m.
PD Predicate disambiguation batch_69f60b8dfa0c8190864e1a940024d0a0 completed May 2, 2026, 2:34 p.m.
Created at: April 27, 2026, 4:22 a.m.