Triple
T26191106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocky Peak Ridge |
E654964
|
entity |
| Predicate | hasTypicalAscentSeason |
P1325
|
FINISHED |
| Object | late spring to fall |
—
|
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: late spring to fall | Statement: [Rocky Peak Ridge, hasTypicalAscentSeason, late spring to fall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalAscentSeason Context triple: [Rocky Peak Ridge, hasTypicalAscentSeason, late spring to fall]
-
A.
climbingSeason
chosen
Indicates the period during which climbing an object, route, or area is typically allowed, feasible, or considered optimal.
-
B.
typicalAscentStartPoint
Indicates the usual or most common location from which an ascent or climb is begun.
-
C.
durationTypicalAscent
Indicates the typical amount of time required to complete an ascent.
-
D.
winterAscentKnownFor
Indicates that an entity is recognized or notable specifically for a winter ascent of a particular route, peak, or climb.
-
E.
typicalAscentCombinedWith
Indicates that one ascent or climbing route is normally undertaken together with another as part of a standard or customary combined itinerary.
- 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_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 26, 2026, 8:44 p.m.