Triple
T26165163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panther Peak |
E654228
|
entity |
| Predicate | nearestTrailheadArea |
P11755
|
FINISHED |
| Object | Upper Works |
—
|
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: Upper Works | Statement: [Panther Peak, nearestTrailheadArea, Upper Works]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestTrailheadArea Context triple: [Panther Peak, nearestTrailheadArea, Upper Works]
-
A.
hasNearbyTrailheadFor
chosen
Indicates that one location has a trailhead situated close enough to serve as a convenient access point for another location.
-
B.
nearestMajorTrailPass
Indicates the relationship where a given location is associated with the closest significant trail crossing or pass along a major trail network.
-
C.
hikingTrailPassesNear
Indicates that a hiking trail runs close to, but does not directly intersect or pass through, a specified location or feature.
-
D.
nearbyResortArea
Indicates that a resort area is located close to or within a short distance of a specified place or entity.
-
E.
nearestArea
Indicates that one area is the closest in distance to a given reference point or region compared to all other candidate areas.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 26, 2026, 8:32 p.m.