Triple
T29623721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | south side of Mount Baker |
E755071
|
entity |
| Predicate | hasPopularSkiRoute |
P194359
|
FINISHED |
| Object | Easton Glacier ski descent |
—
|
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: Easton Glacier ski descent | Statement: [south side of Mount Baker, hasPopularSkiRoute, Easton Glacier ski descent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPopularSkiRoute Context triple: [south side of Mount Baker, hasPopularSkiRoute, Easton Glacier ski descent]
-
A.
hasSkiRunsFor
Indicates that something provides or includes ski runs that are suitable or intended for a particular user group or purpose.
-
B.
hasSkiTrails
Indicates that a location or facility includes one or more designated ski trails available for use.
-
C.
hasSkiAreaAccess
Indicates that an entity provides direct access to, or is directly connected with, a ski area or ski facilities.
-
D.
hasSkiRaceCourse
Indicates that an entity includes, contains, or is associated with a designated ski race course.
-
E.
hasSkiResortFeature
Indicates that a ski resort possesses or offers a specific feature, amenity, or characteristic.
- F. None of above. chosen
Provenance (4 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
| PDg | Predicate description generation | batch_69fd6dbc3ac0819093fbcfe95f12b93d |
completed | May 8, 2026, 4:59 a.m. |
Created at: April 28, 2026, 6:36 p.m.