Triple
T21553422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hualālai Northwest Rift Zone |
E531823
|
entity |
| Predicate | hasVolcanicVents |
P144215
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hualālai Northwest Rift Zone, hasVolcanicVents, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVolcanicVents Context triple: [Hualālai Northwest Rift Zone, hasVolcanicVents, yes]
-
A.
hasVolcano
Indicates that one entity possesses, contains, or is the location of a volcano.
-
B.
hasVolcanicActivity
Indicates that the subject exhibits or is associated with ongoing or past volcanic processes, such as eruptions, lava flows, or related geothermal activity.
-
C.
isVolcanic
Indicates that something is characterized by or related to volcanic activity, such as originating from, produced by, or associated with a volcano.
-
D.
hasFumaroles
Indicates the presence of fumaroles (openings emitting volcanic gases or steam) associated with an entity.
-
E.
hasVolcanicProduct
Indicates that an entity possesses, contains, or is associated with material or products originating from volcanic activity.
- F. None of above. chosen
Provenance (4 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeb594956c8190a5b4d81911e3927d |
completed | April 27, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:29 p.m.