Triple
T17124409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diamir Face |
E415553
|
entity |
| Predicate | hasApproximateElevationToSummit |
P45909
|
FINISHED |
| Object | 8126 metres |
—
|
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: 8126 metres | Statement: [Diamir Face, hasApproximateElevationToSummit, 8126 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateElevationToSummit Context triple: [Diamir Face, hasApproximateElevationToSummit, 8126 metres]
-
A.
elevationApproxMeters
chosen
Indicates the approximate elevation of an entity above sea level, measured in meters.
-
B.
hasApproxElevationFeet
Indicates that an entity is associated with an elevation value measured in feet that is approximate rather than exact.
-
C.
distanceToSummit
Indicates the measured or estimated distance remaining from a given point to the summit of a feature or elevation.
-
D.
highestPassApproxElevation
Indicates the approximate elevation of the highest pass along a given route or within a specified area.
-
E.
positionRelativeToSummit
Indicates the spatial relationship of an entity’s location with respect to the summit of a feature or structure.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f025fce481908e261f2e363e14f9 |
completed | April 18, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69e35d6d20808190a38bb32e2294bc48 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:36 a.m.