Triple
T24309857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sørbreen |
E612639
|
entity |
| Predicate | hasVolcanicContext |
P41618
|
FINISHED |
| Object | Beerenberg stratovolcano |
—
|
NE NERFINISHED |
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: Beerenberg stratovolcano | Statement: [Sørbreen, hasVolcanicContext, Beerenberg stratovolcano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVolcanicContext Context triple: [Sørbreen, hasVolcanicContext, Beerenberg stratovolcano]
-
A.
hasVolcano
Indicates that one entity possesses, contains, or is the location of a volcano.
-
B.
containsVolcanoType
chosen
Indicates that a geographic area or feature includes at least one volcano of the specified type.
-
C.
hasVolcanicActivity
Indicates that the subject exhibits or is associated with ongoing or past volcanic processes, such as eruptions, lava flows, or related geothermal activity.
-
D.
hasVolcanicProduct
Indicates that an entity possesses, contains, or is associated with material or products originating from volcanic activity.
-
E.
isVolcanic
Indicates that something is characterized by or related to volcanic activity, such as originating from, produced by, or associated with a volcano.
- 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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29229af3c8190950b70fe5a8dbf6f |
completed | April 29, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:33 a.m.