Triple
T3762192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandia Peak Tramway |
E82186
|
entity |
| Predicate | bottomElevation |
P15473
|
FINISHED |
| Object | about 1,950 meters above sea level |
—
|
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 1,950 meters above sea level | Statement: [Sandia Peak Tramway, bottomElevation, about 1,950 meters above sea level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bottomElevation Context triple: [Sandia Peak Tramway, bottomElevation, about 1,950 meters above sea level]
-
A.
lowestPoint
Indicates that one entity is the point with the minimum vertical position or value relative to another entity or within a specified context.
-
B.
elevationLowerThan
Indicates that the elevation of one entity is lower than the elevation of another entity.
-
C.
elevationMinApprox
Indicates an approximate value for the minimum elevation associated with an entity or location.
-
D.
elevationMinM
Indicates the minimum elevation, measured in meters, at which an entity or phenomenon occurs or is situated.
-
E.
elevationAtBase
chosen
Indicates the height or altitude measured at the base or lowest point of an object or feature relative to a reference level.
- 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_69ad8b1db40081908b61ffa6b78afd4d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcbfa44ac819082f2c895d96c9170 |
completed | March 8, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69adc04c851c8190ae5eaebf36df539b |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.