Triple

T23171766
Position Surface form Disambiguated ID Type / Status
Subject 2012 Emilia earthquakes E578878 entity
Predicate seismogenicType P28044 FINISHED
Object reverse faulting 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: reverse faulting | Statement: [2012 Emilia earthquakes, seismogenicType, reverse faulting]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: seismogenicType
Context triple: [2012 Emilia earthquakes, seismogenicType, reverse faulting]
  • A. earthquakeType chosen
    Indicates the specific classification or category of an earthquake based on its characteristics or cause.
  • B. seismicityCause
    Indicates that one factor or event is the cause or source of observed seismic activity in another context or location.
  • C. tectonicActivityCharacteristic
    Indicates a characteristic or property that describes the nature, intensity, or pattern of tectonic activity associated with something.
  • D. seismicEvent
    Indicates the occurrence of a naturally or artificially induced ground-shaking event, such as an earthquake or tremor, at a specific place and time.
  • E. seismicSignificance
    Indicates the degree to which something is relevant, influential, or important in the context of seismic activity or earthquake-related phenomena.
  • 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_69e245fd2a388190b814c0dfa15f7148 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18f3007108190bc3c831f81ae1dce completed April 29, 2026, 4:55 a.m.
PD Predicate disambiguation batch_69ef89ff76808190808ee4ad9dea776b completed April 27, 2026, 4:08 p.m.
Created at: April 17, 2026, 4:03 p.m.