Triple

T13657462
Position Surface form Disambiguated ID Type / Status
Subject Kagoshima E326897 entity
Predicate volcanicActivityNearby P2857 FINISHED
Object frequent ash emissions from Sakurajima 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 ash emissions from Sakurajima | Statement: [Kagoshima, volcanicActivityNearby, frequent ash emissions from Sakurajima]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: volcanicActivityNearby
Context triple: [Kagoshima, volcanicActivityNearby, frequent ash emissions from Sakurajima]
  • A. volcanoTypeNearby
    Indicates that one entity is located near another entity that is classified as a particular type of volcano.
  • B. nearVolcano
    Indicates that one entity is located in close proximity to a volcano.
  • C. hasVolcanicActivity chosen
    Indicates that the subject exhibits or is associated with ongoing or past volcanic processes, such as eruptions, lava flows, or related geothermal activity.
  • D. volcanicStatus
    Indicates the current activity state or condition of a volcano, such as active, dormant, or extinct.
  • E. isVolcanicNeighborOf
    Indicates that one geographic feature is located close enough to another volcanic feature that they are considered neighboring volcano-related entities.
  • 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_69d8076d8270819092afc2f0e9c359a8 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbc61d56e4819084ae3c16ecdf4a05 completed April 12, 2026, 4:19 p.m.
PD Predicate disambiguation batch_69dbbe8a027081908d8f884b89707a5e completed April 12, 2026, 3:47 p.m.
Created at: April 9, 2026, 9:52 p.m.