Triple

T17591236
Position Surface form Disambiguated ID Type / Status
Subject Lungern E428451 entity
Predicate isLocatedOnTransportRoute P86982 FINISHED
Object Brünig Pass route 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: Brünig Pass route | Statement: [Lungern, isLocatedOnTransportRoute, Brünig Pass route]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isLocatedOnTransportRoute
Context triple: [Lungern, isLocatedOnTransportRoute, Brünig Pass route]
  • A. situatedOnTransportRoute chosen
    Indicates that one entity is located along, on, or directly adjacent to a specified transport route (such as a road, railway, or shipping lane).
  • B. isPublicTransportRoute
    Indicates that a given route is designated and operated as part of a public transportation system available for general use.
  • C. isInTransportNetwork
    Indicates that an entity is part of, connected to, or contained within a specific transport network or system.
  • D. hasTransportRoute
    Indicates that there exists a designated transportation connection or route linking one entity to another.
  • E. isPublicTransportBackboneOf
    Indicates that one transport system serves as the primary structural and functional core of a region’s overall public transportation network.
  • 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_69d889e1030481909950e140c63255b9 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e469e6e3888190b73a5b6d7e8c0a55 completed April 19, 2026, 5:36 a.m.
PD Predicate disambiguation batch_69e3b4fff0348190b899a32da537eaca completed April 18, 2026, 4:44 p.m.
Created at: April 10, 2026, 5:51 a.m.