Triple
T26165162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panther Peak |
E654228
|
entity |
| Predicate | accessedViaTrailhead |
P30481
|
FINISHED |
| Object | Bradley Pond trailhead (near 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: Bradley Pond trailhead (near Upper Works) | Statement: [Panther Peak, accessedViaTrailhead, Bradley Pond trailhead (near Upper Works)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessedViaTrailhead Context triple: [Panther Peak, accessedViaTrailhead, Bradley Pond trailhead (near Upper Works)]
-
A.
accessTrailhead
chosen
Indicates that an entity has a way to reach or enter a specific trailhead location.
-
B.
accessTrailheadArea
Indicates that an entity is permitted to enter or use a designated trailhead area.
-
C.
alternativeTrailhead
Indicates that one trailhead serves as an alternative starting point or access location for the same trail as another trailhead.
-
D.
standardTrailhead
Indicates that a location serves as a designated, officially recognized starting point for a trail.
-
E.
trailheadFacility
Indicates that a facility or amenity is located at or directly associated with a trailhead.
- 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_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 26, 2026, 8:32 p.m.