Triple
T31714044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fellhorn/Kanzelwand ski area |
E809405
|
entity |
| Predicate | hasInterconnectedSlopes |
P199911
|
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, hasInterconnectedSlopes, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInterconnectedSlopes Context triple: [Fellhorn/Kanzelwand ski area, hasInterconnectedSlopes, yes]
-
A.
hasSlopeFeature
Indicates that an entity possesses or is characterized by a particular slope-related property or feature.
-
B.
usesIntermediateSlope
Indicates that an entity employs or operates on a slope of intermediate steepness as part of its process or behavior.
-
C.
isOnSlopeOf
Indicates that one entity is located on the inclined surface or side of another entity, typically a sloping terrain or structure.
-
D.
hasColorfulSlopes
Indicates that the subject has slopes characterized by bright or varied colors.
-
E.
hasSlopeProtection
Indicates that a slope or embankment is equipped with protective measures or structures to prevent erosion, instability, or damage.
- 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff63e6b61081909c648bf0ff279481 |
completed | May 9, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ff6381867881908ae0545df4b71df5 |
completed | May 9, 2026, 4:40 p.m. |
| PDg | Predicate description generation | batch_69ff63e5c35081908f69ac44e12b8f52 |
completed | May 9, 2026, 4:42 p.m. |
Created at: April 30, 2026, 11:16 p.m.