Triple
T37936292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 Nanga Parbat rescue of Élisabeth Revol |
E946358
|
entity |
| Predicate | startingAltitudeOfRescueClimb |
P203303
|
FINISHED |
| Object | around 4900 metres |
—
|
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: around 4900 metres | Statement: [2018 Nanga Parbat rescue of Élisabeth Revol, startingAltitudeOfRescueClimb, around 4900 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startingAltitudeOfRescueClimb Context triple: [2018 Nanga Parbat rescue of Élisabeth Revol, startingAltitudeOfRescueClimb, around 4900 metres]
-
A.
meetsAtAltitude
Indicates that two or more entities come together or intersect at a specific vertical height or elevation.
-
B.
operationalAltitude
Indicates the typical or designated altitude at which an entity is intended to operate.
-
C.
rateOfClimb
Indicates the vertical speed at which an entity ascends or descends over time.
-
D.
hopAltitude
Indicates the vertical distance or height reached by an entity during a hop or jumping motion.
-
E.
extendsFromAltitude
Indicates a relationship where something stretches or reaches outward starting from a specified altitude.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a014f7602988190b8f86cb431a9cf12 |
completed | May 11, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_6a014a70ea748190bd86fb9f218103ba |
completed | May 11, 2026, 3:18 a.m. |
| PDg | Predicate description generation | batch_6a014f751520819088cf1e697e0668ff |
completed | May 11, 2026, 3:39 a.m. |
Created at: May 3, 2026, 4:20 p.m.