Triple
T8054700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandy |
E187767
|
entity |
| Predicate | hasOutdoorAccessTo |
P74338
|
FINISHED |
| Object | ski resorts in the Wasatch Mountains |
—
|
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 resorts in the Wasatch Mountains | Statement: [Sandy, hasOutdoorAccessTo, ski resorts in the Wasatch Mountains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutdoorAccessTo Context triple: [Sandy, hasOutdoorAccessTo, ski resorts in the Wasatch Mountains]
-
A.
hasOutdoorResource
chosen
Indicates that an entity is associated with, provides, or includes access to an outdoor resource or facility.
-
B.
hasOutdoorLocation
Indicates that an entity is associated with or possesses a specific outdoor place or setting.
-
C.
isOutdoorFacility
Indicates that a facility is located outdoors or primarily functions in an open-air environment.
-
D.
hasOutdoorFocus
Indicates a relationship where an entity is primarily concerned with, oriented toward, or specialized in outdoor environments, activities, or contexts.
-
E.
isOutdoor
Indicates that an entity or activity takes place outside, in an open-air or non-enclosed environment.
- 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_69ca82b15e948190a62fd7af5218426a |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f9fb8dc8190bacc1f66ddfd1cbf |
completed | March 31, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69cb049a1b9c8190811c396421ebf9c9 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:25 p.m.