Triple
T31714062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fellhorn/Kanzelwand ski area |
E809405
|
entity |
| Predicate | hasPreparedPistes |
P81970
|
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, hasPreparedPistes, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPreparedPistes Context triple: [Fellhorn/Kanzelwand ski area, hasPreparedPistes, yes]
-
A.
hasGroomedPistes
chosen
Indicates that the subject location or facility provides ski slopes that are regularly maintained and machine-groomed for use.
-
B.
hasPisteType
Indicates that an entity (such as a ski run or trail) is associated with a specific type or category of piste.
-
C.
hasSlopePreparation
Indicates that an entity includes or is associated with preparatory work or treatment specifically related to a slope.
-
D.
hasOffPisteTerrain
Indicates that a location or ski area includes terrain that is off the groomed or marked pistes, typically ungroomed or backcountry skiable areas.
-
E.
hasPilotis
Indicates that a building or structure is elevated on pilotis (supporting columns or stilts), rather than resting directly on the ground.
- 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_6a007dd341108190a1d03eab46041694 |
completed | May 10, 2026, 12:45 p.m. |
| PD | Predicate disambiguation | batch_6a007b1fe2a881909ec50a1e65e4651b |
completed | May 10, 2026, 12:33 p.m. |
Created at: April 30, 2026, 11:16 p.m.