Triple
T6219015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kauaʻi shield volcano |
E139063
|
entity |
| Predicate | hasEruptiveStyle |
P68967
|
FINISHED |
| Object | effusive eruptions |
—
|
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: effusive eruptions | Statement: [Kauaʻi shield volcano, hasEruptiveStyle, effusive eruptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEruptiveStyle Context triple: [Kauaʻi shield volcano, hasEruptiveStyle, effusive eruptions]
-
A.
erupted
Indicates that a volcano or similar geological feature suddenly expelled lava, ash, gas, or other material in a violent outburst.
-
B.
eruptionSeriesOf
Indicates a relationship where a specific volcanic eruption is a member event within a broader series or sequence of related eruptions.
-
C.
isExplosiveVolcano
Indicates that a volcano is currently or typically capable of explosive eruptions, characterized by violent release of gas, ash, and pyroclastic material.
-
D.
eruptionFrequency
Indicates how often an eruption event occurs within a given time period.
-
E.
notableEruption
Indicates that a volcano or geothermal feature has experienced an eruption considered historically or scientifically significant.
- 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_69c008aecb0c81909984b48f733ce8ae |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062a481908190a1418d9fcfaf8137 |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055ffdf54819086d987d646e44ff5 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056c965ac8190b938502fa8c74e1b |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:21 p.m.