Triple

T4201605
Position Surface form Disambiguated ID Type / Status
Subject 2011 Tōhoku earthquake and tsunami E86077 entity
Predicate notableAftershock P3828 FINISHED
Object Mw 7.9 aftershock on 2011-03-11 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: Mw 7.9 aftershock on 2011-03-11 | Statement: [2011 Tōhoku earthquake and tsunami, notableAftershock, Mw 7.9 aftershock on 2011-03-11]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableAftershock
Context triple: [2011 Tōhoku earthquake and tsunami, notableAftershock, Mw 7.9 aftershock on 2011-03-11]
  • A. notableEarthquake
    Indicates that an earthquake event is significant or noteworthy due to its magnitude, impact, or historical importance.
  • B. aftershocks chosen
    Indicates that one seismic event occurs as a subsequent, typically smaller tremor following a main earthquake.
  • C. notableEruption
    Indicates that a volcano or geothermal feature has experienced an eruption considered historically or scientifically significant.
  • D. notableDuring
    Indicates that something was especially prominent, active, or significant during a particular time period or event.
  • E. facedMajorEarthquake
    Indicates that an entity has experienced or been subjected to a significant or severe earthquake event.
  • 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_69aed93b89f48190a31f6d57c760e42f completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af037da30481908106b27a88d59140 completed March 9, 2026, 5:29 p.m.
PD Predicate disambiguation batch_69af01959c4881909eb1adcb3bdadbe6 completed March 9, 2026, 5:21 p.m.
Created at: March 9, 2026, 3:49 p.m.