Triple
T14712657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UTMB |
E345589
|
entity |
| Predicate | approximateElevationGainMeters |
P30489
|
FINISHED |
| Object | 10000 |
—
|
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: 10000 | Statement: [UTMB, approximateElevationGainMeters, 10000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateElevationGainMeters Context triple: [UTMB, approximateElevationGainMeters, 10000]
-
A.
hasApproxElevationGainFt
Indicates that one entity is associated with an approximate amount of elevation gain, measured in feet, relative to another context or reference.
-
B.
elevationGainRelativeToBase
Indicates the amount of elevation increase of something compared to a defined base level.
-
C.
elevationApproxMeters
Indicates the approximate elevation of an entity above sea level, measured in meters.
-
D.
approximateElevationGainFromParadise
Indicates the estimated amount of elevation gained when traveling from the location named Paradise to another specified point or along a specified route.
-
E.
totalAscent
chosen
Indicates the total cumulative elevation gained over the course of a movement, route, or activity.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb982bf248190881e21a8a0861a3f |
completed | April 14, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.