Triple
T26191109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocky Peak Ridge |
E654964
|
entity |
| Predicate | hasTrailDifficultyRating |
P24163
|
FINISHED |
| Object | strenuous day hike |
—
|
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: strenuous day hike | Statement: [Rocky Peak Ridge, hasTrailDifficultyRating, strenuous day hike]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrailDifficultyRating Context triple: [Rocky Peak Ridge, hasTrailDifficultyRating, strenuous day hike]
-
A.
hasTrailDifficulty
chosen
Indicates the level of challenge or effort required to traverse a particular trail or route.
-
B.
hasSlopeRating
Indicates that something (typically a golf course or hole) is associated with a specific slope rating value that quantifies its relative difficulty for bogey golfers compared to scratch golfers.
-
C.
reachableFromTrailhead
Indicates that a location or segment can be accessed by traveling from a designated trailhead.
-
D.
относитсяККатегорииСложностиВосхождений
Indicates that something is associated with a specific category of climbing difficulty.
-
E.
hasClimbingTrail
Indicates that a location or area includes or provides access to a designated climbing trail.
- 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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 26, 2026, 8:44 p.m.