Triple
T31128440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snow Park base area |
E793422
|
entity |
| Predicate | hasLodgingAccess |
P181081
|
FINISHED |
| Object | Deer Valley area hotels |
—
|
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: Deer Valley area hotels | Statement: [Snow Park base area, hasLodgingAccess, Deer Valley area hotels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLodgingAccess Context triple: [Snow Park base area, hasLodgingAccess, Deer Valley area hotels]
-
A.
hasAccommodation
Indicates that an entity provides, owns, or is associated with a place for someone to stay or live.
-
B.
hasAmenityAccessTo
Indicates that an entity has the right or ability to use or benefit from a specified amenity or facility.
-
C.
hasAccommodations
chosen
Indicates that one entity provides, contains, or offers lodging, facilities, or special arrangements for another entity.
-
D.
hasResortAccessTo
Indicates that one entity is permitted to use, enter, or benefit from the facilities or services of a particular resort.
-
E.
hasDayLodge
Indicates that a location or facility includes or is associated with a day-use lodge building or area.
- 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_69f224d1701c819094f429798290e361 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: April 29, 2026, 9:05 p.m.