Triple
T7318856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nevado Tres Cruces |
E168484
|
entity |
| Predicate | isHighAltitude |
P73807
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Nevado Tres Cruces, isHighAltitude, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHighAltitude Context triple: [Nevado Tres Cruces, isHighAltitude, true]
-
A.
isHighElevation
chosen
Indicates that an entity is located at or associated with a relatively high altitude or elevation above a reference level, typically sea level.
-
B.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
C.
altitudeCapability
Indicates the maximum or typical altitude at which an entity can effectively operate or function.
-
D.
hasAltitudeFeature
Indicates that an entity possesses a characteristic or attribute related to its elevation or vertical position above a reference level.
-
E.
altitudeEffect
Indicates how a change in altitude influences or modifies some property, condition, or outcome.
- 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_69c68a5251508190ad68df4151cfeb04 |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6ef18b7bc81908a9ee405d684f304 |
completed | March 27, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:02 p.m.