Triple

T4624024
Position Surface form Disambiguated ID Type / Status
Subject Halifax Explosion E101051 entity
Predicate aftershockEvent P3828 FINISHED
Object blizzard on 1917-12-07 hampering rescue efforts 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: blizzard on 1917-12-07 hampering rescue efforts | Statement: [Halifax Explosion, aftershockEvent, blizzard on 1917-12-07 hampering rescue efforts]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: aftershockEvent
Context triple: [Halifax Explosion, aftershockEvent, blizzard on 1917-12-07 hampering rescue efforts]
  • A. aftershocks chosen
    Indicates that one seismic event occurs as a subsequent, typically smaller tremor following a main earthquake.
  • B. notableAftershockMagnitude
    Indicates that the magnitude value corresponds to a particularly significant or noteworthy aftershock following a main seismic event.
  • C. earthquakeSequence
    Indicates a relationship where multiple earthquakes are linked as part of the same temporal or causal sequence of seismic events.
  • D. notableEarthquake
    Indicates that an earthquake event is significant or noteworthy due to its magnitude, impact, or historical importance.
  • E. earthquakeType
    Indicates the specific classification or category of an earthquake based on its characteristics or cause.
  • 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_69bd43d0497c8190ac23c65c5804846a completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd5a06d6248190a613be9784dd1ef4 completed March 20, 2026, 2:30 p.m.
PD Predicate disambiguation batch_69bd5231db7c8190b38d4fdbad8bf842 completed March 20, 2026, 1:57 p.m.
Created at: March 20, 2026, 1:13 p.m.