Triple
T26302201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Hierro volcano |
E661585
|
entity |
| Predicate | islandHighestPointElevation_m |
P152433
|
FINISHED |
| Object | 1501 |
—
|
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: 1501 | Statement: [El Hierro volcano, islandHighestPointElevation_m, 1501]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: islandHighestPointElevation_m Context triple: [El Hierro volcano, islandHighestPointElevation_m, 1501]
-
A.
elevationOfHighestPeak_ft
Indicates the height, in feet, of the tallest peak associated with the given entity.
-
B.
hasHighestPointAboveSeaLevel
Indicates that the highest point of one entity is located at a greater elevation above sea level than that of another entity.
-
C.
countryHighestPointAccess
Indicates that an entity has access to, or the ability to reach or utilize, the highest geographical point within a specified country.
-
D.
prominenceOfHighestPeak_m
Indicates the vertical prominence, in meters, of the highest peak relative to the lowest contour line encircling it and no higher summit.
-
E.
mountainHeight
chosen
Indicates the vertical elevation or height of a mountain, typically measured from sea level.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60eb396788190a225665a56568d2c |
completed | May 2, 2026, 2:48 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 10:16 p.m.