Triple
T29128394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ontake-san |
E738297
|
entity |
| Predicate | 2014EruptionFatalities |
P82247
|
FINISHED |
| Object | over 60 people |
—
|
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: over 60 people | Statement: [Ontake-san, 2014EruptionFatalities, over 60 people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2014EruptionFatalities Context triple: [Ontake-san, 2014EruptionFatalities, over 60 people]
-
A.
casualtiesIn2014Eruption
chosen
Indicates the number of people who were killed or injured as a result of the eruption that occurred in 2014.
-
B.
eruptionVEI
Indicates the Volcanic Explosivity Index (VEI) assigned to a particular volcanic eruption event.
-
C.
eruptionObserved
Indicates that an eruption event has been witnessed, detected, or recorded by an observer or observing system.
-
D.
eruptionDate
Indicates the specific date on which an eruption event occurs or is recorded.
-
E.
notableEruption
Indicates that a volcano or geothermal feature has experienced an eruption considered historically or scientifically significant.
- 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_69f07cb29cdc8190afa55444553de60c |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6622c2e1c819093b43ecb65f3fa52 |
completed | May 2, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:30 a.m.