Triple
T24461348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reykjanes Peninsula |
E616835
|
entity |
| Predicate | hasVolcanicSystem |
P47953
|
FINISHED |
| Object | Reykjanes volcanic system |
—
|
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: Reykjanes volcanic system | Statement: [Reykjanes Peninsula, hasVolcanicSystem, Reykjanes volcanic system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVolcanicSystem Context triple: [Reykjanes Peninsula, hasVolcanicSystem, Reykjanes volcanic system]
-
A.
isPartOfVolcanicSystem
chosen
Indicates that one entity belongs to, or is a component within, a larger volcanic system or complex.
-
B.
hasVolcano
Indicates that one entity possesses, contains, or is the location of a volcano.
-
C.
hasVolcanicVents
Indicates that one entity possesses or contains volcanic vents associated with another entity or location.
-
D.
isVolcanic
Indicates that something is characterized by or related to volcanic activity, such as originating from, produced by, or associated with a volcano.
-
E.
hasVolcanicActivity
Indicates that the subject exhibits or is associated with ongoing or past volcanic processes, such as eruptions, lava flows, or related geothermal activity.
- 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_69e2d7ef9fe08190a0613908758b4e86 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f298ca59088190a657c863713a9eb0 |
completed | April 29, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:19 a.m.