Triple
T26689475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunrise Lakes |
E672835
|
entity |
| Predicate | hikingTrailPassesNear |
P161117
|
FINISHED |
| Object | trail to Clouds Rest |
—
|
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: trail to Clouds Rest | Statement: [Sunrise Lakes, hikingTrailPassesNear, trail to Clouds Rest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hikingTrailPassesNear Context triple: [Sunrise Lakes, hikingTrailPassesNear, trail to Clouds Rest]
-
A.
hasNearbyTrailheadFor
Indicates that one location has a trailhead situated close enough to serve as a convenient access point for another location.
-
B.
isHikingTrail
Indicates that a path or route is designated and used specifically for hiking activities.
-
C.
nearestMajorTrailPass
Indicates the relationship where a given location is associated with the closest significant trail crossing or pass along a major trail network.
-
D.
hasMountainPassNearby
Indicates that a mountain pass is located in close proximity to the referenced place or feature.
-
E.
hasClimbingTrail
Indicates that a location or area includes or provides access to a designated climbing trail.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61741857c81909cbe2fa1583dcaec |
completed | May 2, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60f24ed608190bffe6c6084fc2f7a |
completed | May 2, 2026, 2:50 p.m. |
Created at: April 27, 2026, 3:25 a.m.