Triple
T14833113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unzen |
E348757
|
entity |
| Predicate | 1991EruptionFeature |
P116007
|
FINISHED |
| Object | frequent pyroclastic flows |
—
|
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: frequent pyroclastic flows | Statement: [Unzen, 1991EruptionFeature, frequent pyroclastic flows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 1991EruptionFeature Context triple: [Unzen, 1991EruptionFeature, frequent pyroclastic flows]
-
A.
eruption1902Type
Indicates the specific classification or type of the 1902 eruption event associated with an entity.
-
B.
2019EruptionType
Indicates the specific type or classification of eruption that occurred in 2019 for the related entity.
-
C.
eruptionObserved
Indicates that an eruption event has been witnessed, detected, or recorded by an observer or observing system.
-
D.
notableEruption
Indicates that a volcano or geothermal feature has experienced an eruption considered historically or scientifically significant.
-
E.
eruptionVolcano
Indicates that a volcanic eruption event is occurring at or is associated with a specific volcano.
- 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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded075af0881908fb35a9e7ee46749 |
completed | April 14, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de90806f3881908fcbfec5bd4ab4d2 |
completed | April 14, 2026, 7:07 p.m. |
Created at: April 10, 2026, 1:52 a.m.