Triple
T90184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atacama Desert |
E1812
|
entity |
| Predicate | hasElevationRange |
P1977
|
FINISHED |
| Object | from sea level to over 4000 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: from sea level to over 4000 meters | Statement: [Atacama Desert, hasElevationRange, from sea level to over 4000 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElevationRange Context triple: [Atacama Desert, hasElevationRange, from sea level to over 4000 meters]
-
A.
typicalElevationRange
chosen
Indicates the usual range of elevation values within which something commonly occurs or exists.
-
B.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
C.
hasMountainRange
Indicates that one entity possesses, contains, or is geographically associated with a specific mountain range.
-
D.
mountainRange
Indicates that one entity is a mountain range that the other entity is part of, associated with, or located in.
-
E.
hasSalinityRange
Indicates the range of salinity values within which something (such as a substance, environment, or organism) is present, applicable, or able to function.
- 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_69a24d1a97dc819094e6c021fe9b05a7 |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a24feef1b08190bb9525f71cce053e |
completed | Feb. 28, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69a24eb82d408190b0f9c786152e8e4c |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:07 a.m.