Triple
T34522713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Cordillera of the Andes |
E886319
|
entity |
| Predicate | highestZones |
P193499
|
FINISHED |
| Object | exceed 5,000 metres in some peaks |
—
|
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: exceed 5,000 metres in some peaks | Statement: [Eastern Cordillera of the Andes, highestZones, exceed 5,000 metres in some peaks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestZones Context triple: [Eastern Cordillera of the Andes, highestZones, exceed 5,000 metres in some peaks]
-
A.
higherZonesContribution
Indicates that one entity contributes more or plays a greater role in higher zones or levels than another entity.
-
B.
lowestZone
Indicates that one entity occupies or corresponds to the lowest-ranked or lowest-level zone among a set of zones.
-
C.
regionTallestUntil
Indicates that an entity is the tallest within a specified region up to, but not necessarily after, a given point in time.
-
D.
numberOfZones
Indicates the quantity of distinct zones associated with or contained by a given entity.
-
E.
outermostZone
Indicates that one entity is the outermost or furthest boundary zone enclosing or surrounding another entity or area.
- F. None of above. chosen
Provenance (4 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69fd485e0c20819099756b4fe39ac326 |
completed | May 8, 2026, 2:20 a.m. |
Created at: May 1, 2026, 2:02 a.m.