Triple
T26018981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Osprey at Beaver Creek |
E647104
|
entity |
| Predicate | skiInSkiOutAccess |
P123584
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Osprey at Beaver Creek, skiInSkiOutAccess, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skiInSkiOutAccess Context triple: [The Osprey at Beaver Creek, skiInSkiOutAccess, true]
-
A.
hasSkiInSkiOutAccess
chosen
Indicates that a property or accommodation provides direct access to ski slopes without needing transportation or significant walking distance.
-
B.
hasSkiAreaAccess
Indicates that an entity provides direct access to, or is directly connected with, a ski area or ski facilities.
-
C.
hasSkiTrails
Indicates that a location or facility includes one or more designated ski trails available for use.
-
D.
isSkiDestination
Indicates that a place serves as a location suitable or commonly used for skiing activities.
-
E.
hasNightSkiing
Indicates that a location or facility offers skiing activities that take place during nighttime under artificial lighting.
- 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_69e77e8aa65881909ca58918f29ab2a0 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605bbb17c819080f6b026c2cbc186 |
completed | May 2, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69f4a10728e08190bc0b96c558740f51 |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 9:03 a.m.