Triple
T28813173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 御嶽山 |
E727570
|
entity |
| Predicate | 2014年噴火の特徴 |
P166505
|
FINISHED |
| Object | 前兆が小さい突発的噴火 |
—
|
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: 前兆が小さい突発的噴火 | Statement: [御嶽山, 2014年噴火の特徴, 前兆が小さい突発的噴火]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2014年噴火の特徴 Context triple: [御嶽山, 2014年噴火の特徴, 前兆が小さい突発的噴火]
-
A.
casualtiesIn2014Eruption
Indicates the number of people who were killed or injured as a result of the eruption that occurred in 2014.
-
B.
eruptionName
Indicates the specific name assigned to a volcanic eruption event associated with an entity.
-
C.
eruptionEffect
Indicates the impact or consequences that an eruption has on its surrounding environment, systems, or entities.
-
D.
typeOfVolcanicFeature
Indicates that one entity is classified as a specific kind or category of volcanic feature represented by the other entity.
-
E.
eruptionObserved
Indicates that an eruption event has been witnessed, detected, or recorded by an observer or observing system.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6622808b48190bbabcc75288ab031 |
completed | May 2, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f6617a7e7c81908cfac4a2250797ee |
completed | May 2, 2026, 8:41 p.m. |
Created at: April 28, 2026, 6:31 a.m.