Triple
T32158230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taupō volcano |
E821354
|
entity |
| Predicate | producedEruption |
P195192
|
FINISHED |
| Object | Ōruanui eruption |
—
|
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: Ōruanui eruption | Statement: [Taupō volcano, producedEruption, Ōruanui eruption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producedEruption Context triple: [Taupō volcano, producedEruption, Ōruanui eruption]
-
A.
eruptedThrough
Indicates that one entity forcefully broke out from within and passed through another entity, typically in a sudden or violent manner.
-
B.
eruptionSeriesOf
Indicates a relationship where a specific volcanic eruption is a member event within a broader series or sequence of related eruptions.
-
C.
eruptionPhenomena
Indicates the specific observable events or manifestations that occur during a volcanic eruption.
-
D.
eruptionFormed
Indicates that one entity was created or brought into existence as a direct result of a volcanic eruption involving the other entity.
-
E.
materialErupted
Indicates that some material has been expelled or discharged forcefully from a source, such as through an eruption or sudden outburst.
- 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_69f34905e098819082191a6922a6d607 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69fdb04d37288190969a0f39d92efb49 |
completed | May 8, 2026, 9:43 a.m. |
Created at: May 1, 2026, 12:32 a.m.