Triple
T2356794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Mile Trail |
E47573
|
entity |
| Predicate | upperTrailhead |
P11755
|
FINISHED |
| Object | near Glacier Point parking area |
—
|
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: near Glacier Point parking area | Statement: [Four Mile Trail, upperTrailhead, near Glacier Point parking area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperTrailhead Context triple: [Four Mile Trail, upperTrailhead, near Glacier Point parking area]
-
A.
trailName
Indicates the name assigned to a specific trail or path in the relationship.
-
B.
trailblazerFor
Indicates that one entity serves as a pioneering example, opening the way or setting a precedent for another entity to follow or build upon.
-
C.
nearestSummit
Indicates that one summit is the closest in distance to a given reference point or location compared to all other summits.
-
D.
TrailLinkIs
Indicates that one trail segment is connected to or continues from another trail segment.
-
E.
hasNearbyTrailheadFor
chosen
Indicates that one location has a trailhead situated close enough to serve as a convenient access point for another location.
- 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_69a88a1b678c8190bce986922ba60ce0 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abcb802da08190980100444010f91e |
completed | March 7, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69abc5981ce48190a3f7852d28276e11 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:54 p.m.