Triple
T10428756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hemsedal |
E245852
|
entity |
| Predicate | hasOutdoorActivityInfrastructure |
P74338
|
FINISHED |
| Object | ski lifts |
—
|
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: ski lifts | Statement: [Hemsedal, hasOutdoorActivityInfrastructure, ski lifts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutdoorActivityInfrastructure Context triple: [Hemsedal, hasOutdoorActivityInfrastructure, ski lifts]
-
A.
hasOutdoorResource
chosen
Indicates that an entity is associated with, provides, or includes access to an outdoor resource or facility.
-
B.
isOutdoorFacility
Indicates that a facility is located outdoors or primarily functions in an open-air environment.
-
C.
hasOutdoorSpaceType
Indicates the specific kind of outdoor area associated with an entity, such as a balcony, terrace, garden, or patio.
-
D.
outdoorVenue
Indicates that an event, activity, or gathering takes place at a location situated outdoors rather than inside a building or enclosed structure.
-
E.
hasOutdoorPlatforms
Indicates that an entity includes one or more platforms or boarding areas that are located outdoors rather than inside a building or covered structure.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea4b4b5881908ae23f8efeea482b |
completed | April 7, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb9d3648190aaabed901f22a8c0 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:13 p.m.