Triple
T11331371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chimborazo summit expeditions |
E268350
|
entity |
| Predicate | highestElevationReached |
P80409
|
FINISHED |
| Object | 6263 m |
—
|
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: 6263 m | Statement: [Chimborazo summit expeditions, highestElevationReached, 6263 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestElevationReached Context triple: [Chimborazo summit expeditions, highestElevationReached, 6263 m]
-
A.
highestLatitudeReached
Indicates the maximum latitude that an entity has ever reached during its movement or existence.
-
B.
highestPeakAccessed
Indicates that one entity has reached or visited the tallest peak associated with another entity or within a specified context.
-
C.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
D.
highestPassApproxElevation
Indicates the approximate elevation of the highest pass along a given route or within a specified area.
-
E.
elevationRangeUpperBound
chosen
Indicates the maximum elevation value that bounds the upper limit of an elevation range for something.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9fd38308190a5458be1bfcc89ea |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787afe5a48190b8af1a3e19529641 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.