Triple
T11281443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Öræfajökull |
E267073
|
entity |
| Predicate | prominenceOfHighestPeak |
P10298
|
FINISHED |
| Object | 2009 m |
—
|
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: 2009 m | Statement: [Öræfajökull, prominenceOfHighestPeak, 2009 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prominenceOfHighestPeak Context triple: [Öræfajökull, prominenceOfHighestPeak, 2009 m]
-
A.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
B.
areaPeak
Indicates that a specified location or region is the highest point (peak) within a given area or spatial extent.
-
C.
topographicProminence
chosen
Indicates the height of a peak’s summit relative to the lowest contour line encircling it and no higher summit, expressing how much it stands out from surrounding terrain.
-
D.
notablePeak
Indicates that one entity is a peak or summit that is especially prominent, famous, or significant in relation to another entity.
-
E.
territorialPeak
Indicates the highest geographical point located within the territory or jurisdiction of a given entity.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e96e15708190b3a1cccfbbe65882 |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a240588190aa097298f951c915 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:31 p.m.