Triple
T33695632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Climb area of Mount Adams |
E863299
|
entity |
| Predicate | hasTypicalAscentStyle |
P45129
|
FINISHED |
| Object | single-day climb |
—
|
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: single-day climb | Statement: [South Climb area of Mount Adams, hasTypicalAscentStyle, single-day climb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalAscentStyle Context triple: [South Climb area of Mount Adams, hasTypicalAscentStyle, single-day climb]
-
A.
typicalAscentStyle
chosen
Indicates the usual or characteristic manner or technique by which an ascent or climb is performed.
-
B.
hasAscentStage
Indicates that one object is the ascent stage component of another, typically in a multi-stage spacecraft or vehicle.
-
C.
typicalAscentCombinedWith
Indicates that one ascent or climbing route is normally undertaken together with another as part of a standard or customary combined itinerary.
-
D.
notableFreeAscentStyle
Indicates that the relationship specifies the particular style or method used for a notable free ascent of a climb or route.
-
E.
typicalAscentStartPoint
Indicates the usual or most common location from which an ascent or climb is begun.
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
Created at: May 1, 2026, 1:43 a.m.