Triple
T35908268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mauna Ulu eruption |
E1038532
|
entity |
| Predicate | producedLavaFlowsTo |
P60055
|
FINISHED |
| Object | coastal areas of Hawaiʻi Island |
—
|
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: coastal areas of Hawaiʻi Island | Statement: [Mauna Ulu eruption, producedLavaFlowsTo, coastal areas of Hawaiʻi Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producedLavaFlowsTo Context triple: [Mauna Ulu eruption, producedLavaFlowsTo, coastal areas of Hawaiʻi Island]
-
A.
producedEruption
Indicates that an entity caused or generated a particular eruption event.
-
B.
hasLavaFlow
Indicates that one entity exhibits, contains, or is associated with a flow of lava originating from volcanic activity.
-
C.
volcanismExtendedInto
chosen
Indicates that volcanic activity from one area or period continued or spread into another area or period.
-
D.
hasPyroclasticDeposits
Indicates that an entity exhibits or contains accumulations of pyroclastic volcanic material deposited by explosive eruptions.
-
E.
hasLavaDomes
Indicates that the subject volcano possesses one or more lava domes as part of its structure or eruptive features.
- 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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fee25dbca481909e6f1c255122b3a8 |
completed | May 9, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69fee1c8915c8190b08b63e42881f1a9 |
completed | May 9, 2026, 7:27 a.m. |
Created at: May 3, 2026, 4:07 p.m.