Triple
T30479964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Bailey |
E775552
|
entity |
| Predicate | hasWinterAccess |
P103010
|
FINISHED |
| Object | snowcat skiing operations (seasonal) |
—
|
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: snowcat skiing operations (seasonal) | Statement: [Mount Bailey, hasWinterAccess, snowcat skiing operations (seasonal)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWinterAccess Context triple: [Mount Bailey, hasWinterAccess, snowcat skiing operations (seasonal)]
-
A.
hasWinterRoute
Indicates that an entity has an associated route or path specifically designated for use during the winter season.
-
B.
hasWinterSeason
Indicates that an entity experiences or includes a distinct winter season within its annual climate or temporal cycle.
-
C.
hasWinterActivitySeason
Indicates that an entity’s primary period for engaging in a particular activity occurs during the winter season.
-
D.
winterAccessMode
chosen
Indicates how access to something is configured, permitted, or restricted specifically during the winter season.
-
E.
hasFrozenInWinter
Indicates that something becomes or has become frozen during the winter season.
- 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_69f22497341481909c21ba329fadaa6b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 29, 2026, 8:12 p.m.