Triple
T15599865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barranco Wall |
E375002
|
entity |
| Predicate | approximateAscent |
P119395
|
FINISHED |
| Object | about 300 meters of vertical gain |
—
|
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: about 300 meters of vertical gain | Statement: [Barranco Wall, approximateAscent, about 300 meters of vertical gain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateAscent Context triple: [Barranco Wall, approximateAscent, about 300 meters of vertical gain]
-
A.
approximateAscentTime
Indicates the estimated amount of time required for an entity to ascend or climb to a specified point or elevation.
-
B.
ashColumnHeightApproximate
Indicates that the height of an ash column is an estimated or approximate value rather than an exact measurement.
-
C.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
-
D.
elevationApproxMeters
Indicates the approximate elevation of an entity above sea level, measured in meters.
-
E.
maximumExtentFromBaseline
Indicates the greatest distance or deviation of something from a defined baseline reference.
- 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_69d85cce25008190b13b52745fbd719b |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e621fc4819097e8e85e7ddfdc6c |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:12 a.m.