Triple
T37327673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abruzzi Spur route on K2 |
E926654
|
entity |
| Predicate | usedForFirstAscentOf |
P193977
|
FINISHED |
| Object | K2 |
—
|
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: K2 | Statement: [Abruzzi Spur route on K2, usedForFirstAscentOf, K2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForFirstAscentOf Context triple: [Abruzzi Spur route on K2, usedForFirstAscentOf, K2]
-
A.
attemptedFirstAscentOf
Indicates that an entity made an effort to be the first to successfully climb or reach the summit of a particular route, peak, or feature.
-
B.
madeFirstWinterAscentWith
Indicates that the subject and the object jointly completed the first successful ascent of a route or peak during winter conditions.
-
C.
coFirstAscentOf
Indicates that multiple climbers or parties share credit for making the first recorded ascent of a particular route, peak, or climbing objective.
-
D.
firstAscent
Indicates that an entity represents the earliest known successful ascent or climb of a particular route, peak, or feature.
-
E.
firstAscentBy
Indicates the person or party that first successfully ascended or climbed a particular route, peak, or feature.
- F. None of above. chosen
Provenance (4 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
| PDg | Predicate description generation | batch_69fd5bf49288819098a12202411cba4f |
completed | May 8, 2026, 3:43 a.m. |
Created at: May 3, 2026, 4:16 p.m.