Triple
T17849898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandstone Peak |
E445770
|
entity |
| Predicate | hasLoopHikeLength |
P30396
|
FINISHED |
| Object | about 6 miles via Mishe Mokwa loop |
—
|
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: about 6 miles via Mishe Mokwa loop | Statement: [Sandstone Peak, hasLoopHikeLength, about 6 miles via Mishe Mokwa loop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLoopHikeLength Context triple: [Sandstone Peak, hasLoopHikeLength, about 6 miles via Mishe Mokwa loop]
-
A.
hikeLength
chosen
Indicates the distance or duration associated with a hiking activity or trail.
-
B.
isHikingTrail
Indicates that a path or route is designated and used specifically for hiking activities.
-
C.
approximateHikeTimeRoundTrip
Indicates the estimated total time required to complete a hike from the starting point to the destination and back to the start.
-
D.
hasNightHiking
Indicates that an entity offers, includes, or is associated with the activity of hiking at night.
-
E.
climbLength
Indicates the total distance or vertical extent covered by a climbing route or ascent.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48ffe415c8190aed351c52b78a143 |
completed | April 19, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:16 a.m.