Triple
T7774791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Páramo de Frontino |
E179163
|
entity |
| Predicate | altitudinalZone |
P35392
|
FINISHED |
| Object | high Andean |
—
|
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: high Andean | Statement: [Páramo de Frontino, altitudinalZone, high Andean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: altitudinalZone Context triple: [Páramo de Frontino, altitudinalZone, high Andean]
-
A.
altitudeCategory
chosen
Indicates the classification of something based on its height or elevation relative to a reference level (e.g., low, medium, high altitude).
-
B.
altitudeProfile
Indicates the variation of elevation or height along a path, route, or trajectory over distance or time.
-
C.
isHighElevation
Indicates that an entity is located at or associated with a relatively high altitude or elevation above a reference level, typically sea level.
-
D.
typicalElevationRange
Indicates the usual range of elevation values within which something commonly occurs or exists.
-
E.
countryAltitudeCharacteristic
Indicates a characteristic relationship specifying the typical or notable altitude or elevation associated with a country.
- 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_69c69f30602c819082ab52cd4af5c592 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c7046331e0819080ec1a5c23c27cd7 |
completed | March 27, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69c7016f4ce881909c2e9f610255187b |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:11 p.m.