Triple
T3947210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belchen |
E92174
|
entity |
| Predicate | hasWinterSportArea |
P18014
|
FINISHED |
| Object | Belchen ski area |
—
|
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: Belchen ski area | Statement: [Belchen, hasWinterSportArea, Belchen ski area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWinterSportArea Context triple: [Belchen, hasWinterSportArea, Belchen ski area]
-
A.
hasWinterSportsSeason
Indicates that an entity participates in, is associated with, or has a defined period for winter sports activities or competitions.
-
B.
hasNightSkiing
Indicates that a location or facility offers skiing activities that take place during nighttime under artificial lighting.
-
C.
hasPopularWinterSports
Indicates that a place or context is associated with winter sports that are widely practiced, enjoyed, or well-attended.
-
D.
hasSkiableArea
chosen
Indicates that an entity possesses an area of terrain that can be used for skiing.
-
E.
hasSkiLifts
Indicates that one location or facility is equipped with ski lifts that provide transportation for skiers or visitors.
- 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_69aed965502c8190904ebad1203a4ae8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee764235081909309b3c982f322a9 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:24 p.m.