Triple
T11220821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deer Valley Resort |
E265555
|
entity |
| Predicate | skiEquipmentPolicy |
P97915
|
FINISHED |
| Object | alpine skis allowed |
—
|
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: alpine skis allowed | Statement: [Deer Valley Resort, skiEquipmentPolicy, alpine skis allowed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skiEquipmentPolicy Context triple: [Deer Valley Resort, skiEquipmentPolicy, alpine skis allowed]
-
A.
hasCampingPolicy
Indicates that an entity specifies rules, restrictions, or guidelines regarding camping activities on its premises or within its jurisdiction.
-
B.
snowboardersAllowed
Indicates that snowboarders are permitted to access or use a particular area, facility, or service.
-
C.
hasSkiPassSystem
Indicates that there exists a ski pass system associated with or implemented at the referenced entity.
-
D.
skiersOnly
Indicates that the associated entity, area, or resource is restricted for use exclusively by skiers and not by other types of users.
-
E.
hasSkiPatrol
Indicates that an entity is served or overseen by a ski patrol responsible for safety and emergency response on the slopes.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8eb84c48190b4f3bede254afde2 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfbbb188190861efd5d94fe27da |
completed | April 9, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69d77062271c8190b63da714ab5beff9 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:30 p.m.