Triple
T26165159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panther Peak |
E654228
|
entity |
| Predicate | hikingDestinationFor |
P103639
|
FINISHED |
| Object | Adirondack Forty-Sixers |
—
|
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: Adirondack Forty-Sixers | Statement: [Panther Peak, hikingDestinationFor, Adirondack Forty-Sixers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hikingDestinationFor Context triple: [Panther Peak, hikingDestinationFor, Adirondack Forty-Sixers]
-
A.
commonAcclimatizationHikeDestinationFrom
Indicates that a location is a typical or frequently used hiking destination for acclimatization starting from a given origin.
-
B.
isHikingDestination
chosen
Indicates that a location serves as a destination or endpoint for hiking activities or routes.
-
C.
hikingUse
Indicates the use or engagement in hiking as an activity or means of travel.
-
D.
trekkingBase
Indicates a location that serves as the primary starting point or support hub for trekking activities.
-
E.
trekkingFeature
Indicates a notable characteristic, condition, or element specifically associated with trekking activities or routes.
- 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_69f60c3e162c819086e1111cdba01ab6 |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 8:32 p.m.