Triple

T9096971
Position Surface form Disambiguated ID Type / Status
Subject Visp E218049 entity
Predicate railwayStationFunction P87142 FINISHED
Object interchange between standard gauge and metre gauge lines 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: interchange between standard gauge and metre gauge lines | Statement: [Visp, railwayStationFunction, interchange between standard gauge and metre gauge lines]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: railwayStationFunction
Context triple: [Visp, railwayStationFunction, interchange between standard gauge and metre gauge lines]
  • A. railwayStationCategory
    Indicates the classification or type category assigned to a railway station within a rail network or system.
  • B. railwayStationFor
    Indicates a relationship where a railway station serves, is designated for, or primarily associated with a particular place, line, or service.
  • C. hasRailwayStation
    Indicates that a place or location is served by, or contains, a railway station.
  • D. hasRailStation
    Indicates that one entity possesses, contains, or is served by a rail station.
  • E. railTerminus
    Indicates that a railway line or service ends at a particular station or location, which serves as its final terminus.
  • 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_69ca83d9844081908e561e367fda6d45 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc96b7d0d48190a3b15f35bef087e3 completed April 1, 2026, 3:53 a.m.
PD Predicate disambiguation batch_69cc65fc7f408190a5846e29ab3b97e5 completed April 1, 2026, 12:25 a.m.
PDg Predicate description generation batch_69cc6a3c78388190a7436acc0e44ff55 completed April 1, 2026, 12:43 a.m.
Created at: March 30, 2026, 7:15 p.m.