Triple
T4665816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peuterey Integral |
E102842
|
entity |
| Predicate | altitudeGain |
P30489
|
FINISHED |
| Object | very large altitude gain from valley to summit |
—
|
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: very large altitude gain from valley to summit | Statement: [Peuterey Integral, altitudeGain, very large altitude gain from valley to summit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: altitudeGain Context triple: [Peuterey Integral, altitudeGain, very large altitude gain from valley to summit]
-
A.
totalAscent
chosen
Indicates the total cumulative elevation gained over the course of a movement, route, or activity.
-
B.
altitudeProfile
Indicates the variation of elevation or height along a path, route, or trajectory over distance or time.
-
C.
altitudeEffect
Indicates how a change in altitude influences or modifies some property, condition, or outcome.
-
D.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
E.
elevationChange
Indicates a change in vertical position or altitude between two points or states.
- F. None of above.
Provenance (3 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_69bd43d9cba4819086c1ab1c2d9d2133 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd655aceb081908100ffc0498fe183 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6215864c8190b50ba0f63ba87d0c |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.