Triple
T31814722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocky Mountains ski areas |
E812103
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | group of ski areas |
C27087
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: group of ski areas Context triple: [Rocky Mountains ski areas, instanceOf, group of ski areas]
-
A.
ski resort network
A ski resort network is an interconnected system of ski areas, facilities, and services that coordinate operations, infrastructure, and guest experiences across multiple mountain locations.
-
B.
ski area
A ski area is a designated mountain or hillside location equipped with ski lifts, groomed trails, and related facilities where people can ski, snowboard, and engage in other winter sports.
-
C.
ski and snowboard pass network
chosen
A ski and snowboard pass network is a system that provides riders access to multiple ski resorts and mountains through a unified pass, often integrating lift access, discounts, and shared services across participating locations.
-
D.
ski area sector
A ski area sector is a distinct, mapped portion of a ski resort comprising specific lifts, runs, and facilities that functions as a recognizable sub-area for navigation, management, and operations.
-
E.
ski lift area
A ski lift area is a designated zone at a ski resort where skiers and snowboarders load onto and unload from ski lifts, often including queues, safety signage, and access control.
- F. None of above.
Provenance (1 batch)
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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:44 p.m.