Triple

T31714066
Position Surface form Disambiguated ID Type / Status
Subject Fellhorn/Kanzelwand ski area E809405 entity
Predicate hasBorderCrossingOnSlopes P4105 FINISHED
Object yes 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: yes | Statement: [Fellhorn/Kanzelwand ski area, hasBorderCrossingOnSlopes, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBorderCrossingOnSlopes
Context triple: [Fellhorn/Kanzelwand ski area, hasBorderCrossingOnSlopes, yes]
  • A. hasSettlementOnSlopes
    Indicates that a settlement is located on or extends across the slopes of a landform such as a hill or mountain.
  • B. hasBorderCrossing chosen
    Indicates that there exists a point or facility where movement or transit is possible between the boundaries of two adjacent regions or jurisdictions.
  • C. crossesBorderOf
    Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
  • D. hasProtectedAreaOnSlopes
    Indicates that a designated protected area exists specifically on the slopes of a landform or terrain.
  • E. hasBorderCrossingSide
    Indicates that one side of a border crossing is associated with or located on a particular boundary or segment of that crossing.
  • 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_69f348df4e048190a4a5a9932ada78d6 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69fd2a215d6c8190a1a428ccaee603f1 completed May 8, 2026, 12:11 a.m.
PD Predicate disambiguation batch_69fd28ef19688190bb8370f2812a43e7 completed May 8, 2026, 12:06 a.m.
Created at: April 30, 2026, 11:16 p.m.