Triple
T31255789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiftcurrent Glacier |
E796965
|
entity |
| Predicate | hasNearestTrailhead |
P11755
|
FINISHED |
| Object | Many Glacier trailheads |
—
|
NE NERFINISHED |
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: Many Glacier trailheads | Statement: [Swiftcurrent Glacier, hasNearestTrailhead, Many Glacier trailheads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearestTrailhead Context triple: [Swiftcurrent Glacier, hasNearestTrailhead, Many Glacier trailheads]
-
A.
hasNearbyTrailheadFor
chosen
Indicates that one location has a trailhead situated close enough to serve as a convenient access point for another location.
-
B.
hasNearbyTrail
Indicates that one entity is located close to or within a short distance of a trail.
-
C.
hasNearbyTrailFeature
Indicates that one entity has another entity as a trail-related feature located in close physical proximity.
-
D.
reachableFromTrailhead
Indicates that a location or segment can be accessed by traveling from a designated trailhead.
-
E.
nearestMajorTrailPass
Indicates the relationship where a given location is associated with the closest significant trail crossing or pass along a major trail network.
- 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_69f224dd5fdc81908a4cd24917b67668 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fedd5a5f4c8190acce88db56303703 |
completed | May 9, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69fed910b31c8190ae837163d146738d |
completed | May 9, 2026, 6:49 a.m. |
Created at: April 29, 2026, 9:12 p.m.