Triple
T31201250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empire Canyon |
E795479
|
entity |
| Predicate | isWithinSkiResort |
P42696
|
FINISHED |
| Object | Deer Valley Resort |
—
|
NE NERFINISHED |
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 Resort | Statement: [Empire Canyon, isWithinSkiResort, Deer Valley Resort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWithinSkiResort Context triple: [Empire Canyon, isWithinSkiResort, Deer Valley Resort]
-
A.
hasSkiResortNearby
Indicates that one location is situated close enough to another location that it can be considered to have a ski resort in its vicinity.
-
B.
isSkiDestination
Indicates that a place serves as a location suitable or commonly used for skiing activities.
-
C.
hasSkiAreaAccess
Indicates that an entity provides direct access to, or is directly connected with, a ski area or ski facilities.
-
D.
hasSkiResortType
Indicates that an entity is associated with, or classified by, a specific type or category of ski resort.
-
E.
isWithinResort
chosen
Indicates that one place, object, or activity is located inside the boundaries of a specific resort.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69bc2ca808190876e5cb05012dbfc |
completed | May 3, 2026, 12:50 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:09 p.m.