Triple
T27789819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cerro de la Silla |
E701049
|
entity |
| Predicate | elevationOfPicoNorte |
P99098
|
FINISHED |
| Object | approximately 1820 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: approximately 1820 m | Statement: [Cerro de la Silla, elevationOfPicoNorte, approximately 1820 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationOfPicoNorte Context triple: [Cerro de la Silla, elevationOfPicoNorte, approximately 1820 m]
-
A.
peakElevationMetres
chosen
Indicates the maximum height of an entity above sea level, measured in metres.
-
B.
elevationOfHighestPeak_ft
Indicates the height, in feet, of the tallest peak associated with the given entity.
-
C.
highestElevationApprox
Indicates that an entity has an approximate value for the maximum elevation reached within its spatial or conceptual extent.
-
D.
rankInNorthAmericaByElevation
Indicates the relative position of a place in an ordered list of locations in North America based on their elevation.
-
E.
mountainPassElevation_ft
Indicates the elevation, measured in feet, at which a mountain pass is located.
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 5:27 p.m.