Triple
T409290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Volcanic Zone of the Andes |
E9450
|
entity |
| Predicate | hasHighPoint |
P8205
|
FINISHED |
| Object | several volcanoes above 6000 metres |
—
|
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: several volcanoes above 6000 metres | Statement: [Central Volcanic Zone of the Andes, hasHighPoint, several volcanoes above 6000 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighPoint Context triple: [Central Volcanic Zone of the Andes, hasHighPoint, several volcanoes above 6000 metres]
-
A.
hasPeak
chosen
Indicates that something possesses or contains a highest point, summit, or maximum value.
-
B.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
C.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
D.
hasProminence
Indicates that one entity stands out in importance, visibility, or influence relative to others within a given context.
-
E.
hasSummit
Indicates that one entity possesses, features, or includes a summit or highest point as part of its structure or characteristics.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ed31681c8190ac32334562fb17fd |
completed | Feb. 28, 2026, 1:27 p.m. |
| PD | Predicate disambiguation | batch_69a2e9737694819080fde9adcc1aa4d4 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.