Triple
T3035254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voie normale du Goûter |
E82992
|
entity |
| Predicate | typicalAscentStyle |
P45129
|
FINISHED |
| Object | two-day ascent with night in a hut |
—
|
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: two-day ascent with night in a hut | Statement: [Voie normale du Goûter, typicalAscentStyle, two-day ascent with night in a hut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAscentStyle Context triple: [Voie normale du Goûter, typicalAscentStyle, two-day ascent with night in a hut]
-
A.
typicalAscentStartPoint
Indicates the usual or most common location from which an ascent or climb is begun.
-
B.
notableFreeAscentStyle
Indicates that the relationship specifies the particular style or method used for a notable free ascent of a climb or route.
-
C.
durationTypicalAscent
Indicates the typical amount of time required to complete an ascent.
-
D.
firstAscentStyle
Indicates the style or manner in which the first successful ascent of a route or peak was carried out.
-
E.
totalAscent
Indicates the total cumulative elevation gained over the course of a movement, route, or activity.
- 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_69ad8b2298908190a7cb4e9bdbf064d0 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9b2a40b48190bfa7cdbb0fbd87f8 |
completed | March 8, 2026, 3:52 p.m. |
| PD | Predicate disambiguation | batch_69ad961e2a408190afb1759132701305 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97ba55dc8190b6dddddfb751cf64 |
completed | March 8, 2026, 3:37 p.m. |
Created at: March 8, 2026, 3:01 p.m.