Triple
T37327678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abruzzi Spur route on K2 |
E926654
|
entity |
| Predicate | startsNearElevation |
P85156
|
FINISHED |
| Object | about 5300 meters |
—
|
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 5300 meters | Statement: [Abruzzi Spur route on K2, startsNearElevation, about 5300 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startsNearElevation Context triple: [Abruzzi Spur route on K2, startsNearElevation, about 5300 meters]
-
A.
elevationBy
Indicates a relationship where one entity raises, increases, or enhances the level, status, or intensity of another entity.
-
B.
nearbyElevation
Indicates that one entity is located at or associated with an elevation that is geographically close to the elevation of another entity.
-
C.
foundInElevation
Indicates that something exists, occurs, or is located at a particular elevation or height above a reference level.
-
D.
typicalStartElevation
chosen
Indicates the usual or characteristic elevation at which something (such as a route, feature, or activity) typically begins.
-
E.
meetsAtAltitude
Indicates that two or more entities come together or intersect at a specific vertical height or elevation.
- 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00c486d394819084fe93d5bb11ea1e |
completed | May 10, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_6a00c39d99d48190a94bfa057213499c |
completed | May 10, 2026, 5:42 p.m. |
Created at: May 3, 2026, 4:16 p.m.