Triple
T33756394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ochsenkopf |
E864989
|
entity |
| Predicate | hasWinterSportsInfrastructure |
P180679
|
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: [Ochsenkopf, hasWinterSportsInfrastructure, ski lifts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWinterSportsInfrastructure Context triple: [Ochsenkopf, hasWinterSportsInfrastructure, ski lifts]
-
A.
hasWinterSports
Indicates that an entity offers, supports, or is associated with winter sports activities.
-
B.
hasWinterSportsResort
Indicates that a location or entity possesses or hosts a resort specifically dedicated to winter sports activities.
-
C.
hasWinterSportsSeason
Indicates that an entity participates in, is associated with, or has a defined period for winter sports activities or competitions.
-
D.
hasPopularWinterSports
Indicates that a place or context is associated with winter sports that are widely practiced, enjoyed, or well-attended.
-
E.
isSkiDestination
Indicates that a place serves as a location suitable or commonly used for skiing activities.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f74654c09c819084879162eba9d641 |
completed | May 3, 2026, 12:57 p.m. |
Created at: May 1, 2026, 1:45 a.m.