Triple
T4713178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Llaima Volcano |
E104565
|
entity |
| Predicate | hadMajorEruption |
P20891
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [Llaima Volcano, hadMajorEruption, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadMajorEruption Context triple: [Llaima Volcano, hadMajorEruption, 2008]
-
A.
notableEruption
Indicates that a volcano or geothermal feature has experienced an eruption considered historically or scientifically significant.
-
B.
eruptionSeriesOf
Indicates a relationship where a specific volcanic eruption is a member event within a broader series or sequence of related eruptions.
-
C.
lastMajorEruptivePeriod
Indicates the most recent significant time span during which a volcano or eruptive system experienced major eruptive activity.
-
D.
majorEruptionYear
chosen
Indicates the calendar year in which a volcano or similar geological feature experienced a major eruption.
-
E.
previousNotableEruption
Indicates that one volcanic eruption directly precedes another notable eruption in time.
- 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_69bd43eac3c08190af7e4020c6c3704c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:18 p.m.