Triple

T34928331
Position Surface form Disambiguated ID Type / Status
Subject eastern Andes E1007353 entity
Predicate hasAltitudinalRange P1977 FINISHED
Object from low foothills to mid-montane elevations 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 low foothills to mid-montane elevations | Statement: [eastern Andes, hasAltitudinalRange, from low foothills to mid-montane elevations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAltitudinalRange
Context triple: [eastern Andes, hasAltitudinalRange, from low foothills to mid-montane elevations]
  • A. typicalElevationRange chosen
    Indicates the usual range of elevation values within which something commonly occurs or exists.
  • B. hasAltitudeDifference
    Indicates that there is a specific vertical height difference between two entities or locations.
  • C. tracksAltitudeRange
    Indicates that something monitors or records the minimum and maximum altitude values over a given period or area.
  • D. hasAltitudeFeature
    Indicates that an entity possesses a characteristic or attribute related to its elevation or vertical position above a reference level.
  • E. altitudeRange_m
    Indicates the range of altitudes, measured in meters, over which the relationship or condition holds.
  • 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_69f76dc3d83881909d5c3c14455cfa2c completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fd9ff026a48190bfec33deeb3b2c43 completed May 8, 2026, 8:33 a.m.
PD Predicate disambiguation batch_69fd97d805bc8190ba12f429d3ad04c7 completed May 8, 2026, 7:59 a.m.
Created at: May 3, 2026, 4 p.m.