Triple
T19449149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hochsölden |
E486564
|
entity |
| Predicate | skiAreaAltitudeRange |
P117028
|
FINISHED |
| Object | approximately 2000–3000 metres |
—
|
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: approximately 2000–3000 metres | Statement: [Hochsölden, skiAreaAltitudeRange, approximately 2000–3000 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skiAreaAltitudeRange Context triple: [Hochsölden, skiAreaAltitudeRange, approximately 2000–3000 metres]
-
A.
skiAreaAltitudeRange_m
chosen
Indicates the range of altitudes, in meters, over which a ski area extends.
-
B.
skiAreaElevationMax
Indicates the maximum elevation, typically in meters or feet, reached within a ski area.
-
C.
hasSkiAreaBaseElevation
Indicates the base elevation at which a ski area is situated.
-
D.
skiAreaName
Indicates that an entity has a specific name used to identify a ski area.
-
E.
hasSkiRunsLength_km
Indicates the total length, in kilometers, of the ski runs associated with an entity.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6338be5a48190973d9ecae853900c |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.