Triple
T8981163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louis Lachenal |
E214528
|
entity |
| Predicate | firstAscentElevationMetres |
P86156
|
FINISHED |
| Object | 8091 |
—
|
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: 8091 | Statement: [Louis Lachenal, firstAscentElevationMetres, 8091]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAscentElevationMetres Context triple: [Louis Lachenal, firstAscentElevationMetres, 8091]
-
A.
firstAscentFrom
Indicates the starting location or route from which the first successful ascent of something (typically a peak or climb) was made.
-
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.
firstAscent
Indicates that an entity represents the earliest known successful ascent or climb of a particular route, peak, or feature.
-
D.
firstAscentBy
Indicates the person or party that first successfully ascended or climbed a particular route, peak, or feature.
-
E.
firstAscentOfHigherSummit
Indicates that the subject entity is the first recorded ascent of a summit that is higher than another referenced summit.
- 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_69ca839ea8b88190922c6a326ffcc0d3 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc67a76f748190a4abad5d53d58fa8 |
completed | April 1, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69cc5edba0f88190b97401636a076d7a |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5febd0a08190b2de6fb422343001 |
completed | March 31, 2026, 11:59 p.m. |
Created at: March 30, 2026, 7:03 p.m.