Triple

T1063454
Position Surface form Disambiguated ID Type / Status
Subject Mount Tambora E22956 entity
Predicate tephraVolume P23011 FINISHED
Object over 100 km3 dense rock equivalent in 1815 eruption 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 100 km3 dense rock equivalent in 1815 eruption | Statement: [Mount Tambora, tephraVolume, over 100 km3 dense rock equivalent in 1815 eruption]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tephraVolume
Context triple: [Mount Tambora, tephraVolume, over 100 km3 dense rock equivalent in 1815 eruption]
  • A. eruptionVEI
    Indicates the Volcanic Explosivity Index (VEI) assigned to a particular volcanic eruption event.
  • B. hasVolcanicExplosivityIndexRange
    Indicates the range of Volcanic Explosivity Index (VEI) values within which a volcano’s or eruption’s explosiveness falls.
  • C. eruptionFrequency
    Indicates how often an eruption event occurs within a given time period.
  • D. typeOfVolcanicFeature
    Indicates that one entity is classified as a specific kind or category of volcanic feature represented by the other entity.
  • E. associatedVolcano
    Indicates that there is a specific volcano linked or connected to the referenced entity, such as by location, impact, or relevance.
  • 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_69a493dada0481909c43649f9843ea91 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b8f85cc08190ae03ac6c84936cc5 completed March 1, 2026, 10:08 p.m.
PD Predicate disambiguation batch_69a4b7359eb881909c868a558861cc18 completed March 1, 2026, 10:01 p.m.
PDg Predicate description generation batch_69a4b7da38888190a118ef20ce4ae9aa completed March 1, 2026, 10:04 p.m.
Created at: March 1, 2026, 7:42 p.m.