Triple
T33974106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hollyburn Mountain |
E871079
|
entity |
| Predicate | hasSnowshoeRoute |
P169765
|
FINISHED |
| Object | marked winter trail to summit |
—
|
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: marked winter trail to summit | Statement: [Hollyburn Mountain, hasSnowshoeRoute, marked winter trail to summit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSnowshoeRoute Context triple: [Hollyburn Mountain, hasSnowshoeRoute, marked winter trail to summit]
-
A.
hasSnowshoeTrails
chosen
Indicates that a location or area includes designated trails suitable for snowshoeing activities.
-
B.
hasWinterRoute
Indicates that an entity has an associated route or path specifically designated for use during the winter season.
-
C.
hasSnowfield
Indicates that an entity possesses, contains, or is characterized by a snow-covered field or area.
-
D.
hasSnowIn
Indicates that snow is present or occurs within a specified location or region.
-
E.
hasWalkingRouteType
Indicates that an entity is associated with a specific type or category of walking route (e.g., trail, path, or walking itinerary).
- 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_69f3499da0188190ab1a4ff06fb06a2a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:50 a.m.