Triple
T18105095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 lower Puna eruption of Kīlauea |
E433328
|
entity |
| Predicate | maxLavaFlowRate |
P109730
|
FINISHED |
| Object | up to 200 cubic meters per second |
—
|
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: up to 200 cubic meters per second | Statement: [2018 lower Puna eruption of Kīlauea, maxLavaFlowRate, up to 200 cubic meters per second]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxLavaFlowRate Context triple: [2018 lower Puna eruption of Kīlauea, maxLavaFlowRate, up to 200 cubic meters per second]
-
A.
hasLavaFlow
Indicates that one entity exhibits, contains, or is associated with a flow of lava originating from volcanic activity.
-
B.
lavaFlowSpeed
chosen
Indicates the rate at which lava moves or flows from its source over a surface.
-
C.
lavaTemperature
Indicates the temperature value associated with lava in a given context or state.
-
D.
lavaViscosity
Indicates the thickness or resistance to flow of lava in a volcanic or geological context.
-
E.
maximumHeightOfWaterJets
Indicates the greatest vertical height that the water jets in a system or installation can reach.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddb9981c8190b33697fbcaa901b3 |
completed | April 19, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.