Triple
T23342627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southeast Ridge route |
E591773
|
entity |
| Predicate | firstAscentViaRouteYear |
P8812
|
FINISHED |
| Object | 1953 |
—
|
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: 1953 | Statement: [Southeast Ridge route, firstAscentViaRouteYear, 1953]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAscentViaRouteYear Context triple: [Southeast Ridge route, firstAscentViaRouteYear, 1953]
-
A.
firstAscentYear
chosen
Indicates the calendar year in which something (typically a route, peak, or climb) was first successfully ascended.
-
B.
firstAscentRouteOf
Indicates that a particular climbing route is the one used for the first successful ascent of a specific peak or climbing objective.
-
C.
firstFreeAscentYear
Indicates the year in which the first successful free ascent of a route or peak was completed.
-
D.
firstAscentBy
Indicates the person or party that first successfully ascended or climbed a particular route, peak, or feature.
-
E.
firstWinterAscentYear
Indicates the year in which the first successful winter ascent of something (such as a mountain or route) was completed.
- 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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f198334dec819081c432b434eb3ba5 |
completed | April 29, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:18 p.m.