Triple

T23655793
Position Surface form Disambiguated ID Type / Status
Subject Hopfgarten im Brixental E584294 entity
Predicate hasMountainRailwayConnectionTo P153052 FINISHED
Object Hohe Salve 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: Hohe Salve | Statement: [Hopfgarten im Brixental, hasMountainRailwayConnectionTo, Hohe Salve]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMountainRailwayConnectionTo
Context triple: [Hopfgarten im Brixental, hasMountainRailwayConnectionTo, Hohe Salve]
  • A. hasPassengerRailConnection
    Indicates that there exists a passenger rail service linking one location or transport node to another.
  • B. hasSkiLiftConnectionTo
    Indicates a relationship where one location is directly connected to another by a ski lift, allowing travel between them via that lift.
  • C. hasSkiLiftConnectionWith
    Indicates a relationship where two locations or areas are directly connected by a ski lift that allows travel between them.
  • D. hasCableCar
    Indicates that one entity possesses, operates, or is served by a cable car system connecting it to other locations or points.
  • E. hasRailwayStationOn
    Indicates that a railway station is located on or serves a particular railway line, route, or network segment.
  • F. None of above. chosen

Provenance (4 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_69e248ffc0888190ae23c4731eb8b7ac completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1b35b19e48190866a19ed8b7086d0 completed April 29, 2026, 7:29 a.m.
PD Predicate disambiguation batch_69f118d7903c8190bb590a71771e93af completed April 28, 2026, 8:30 p.m.
PDg Predicate description generation batch_69f1233300bc8190ac1639bdca1d7d99 completed April 28, 2026, 9:14 p.m.
Created at: April 17, 2026, 6:49 p.m.