Triple
T32443914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian expedition |
E829090
|
entity |
| Predicate | typeOfAscent |
P202188
|
FINISHED |
| Object | first ascent |
—
|
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: first ascent | Statement: [Austrian expedition, typeOfAscent, first ascent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAscent Context triple: [Austrian expedition, typeOfAscent, first ascent]
-
A.
typeOfClimb
Indicates the specific style or category of climbing activity associated with a climb (e.g., bouldering, sport, trad).
-
B.
durationTypicalAscent
Indicates the typical amount of time required to complete an ascent.
-
C.
totalAscent
Indicates the total cumulative elevation gained over the course of a movement, route, or activity.
-
D.
usedForFirstAscentOf
Indicates that something (typically equipment, a route, or a method) was employed in achieving the first successful ascent of a particular peak, wall, or climbing objective.
-
E.
attemptedAscentOf
Indicates an action where an entity makes an effort to climb or ascend another entity, regardless of whether the ascent is completed successfully.
- 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a005e8a2f7c819085bfc6f04b866d87 |
completed | May 10, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_6a005de82ef08190a015b385d1d3443c |
completed | May 10, 2026, 10:28 a.m. |
| PDg | Predicate description generation | batch_6a005e89803c8190ad732ad15affb81f |
completed | May 10, 2026, 10:31 a.m. |
Created at: May 1, 2026, 12:55 a.m.