Triple

T32157835
Position Surface form Disambiguated ID Type / Status
Subject Digdig Fault segment E821345 entity
Predicate seismogenicPotential P34010 FINISHED
Object large-magnitude earthquakes 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: large-magnitude earthquakes | Statement: [Digdig Fault segment, seismogenicPotential, large-magnitude earthquakes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: seismogenicPotential
Context triple: [Digdig Fault segment, seismogenicPotential, large-magnitude earthquakes]
  • A. seismicSignificance
    Indicates the degree to which something is relevant, influential, or important in the context of seismic activity or earthquake-related phenomena.
  • B. seismicityCause
    Indicates that one factor or event is the cause or source of observed seismic activity in another context or location.
  • C. seismicMoment
    Indicates the relationship between an earthquake event and the total energy it releases, quantified as its seismic moment.
  • D. earthquakeHazardLevel chosen
    Indicates the assessed degree of risk or potential impact from earthquakes associated with a given location or entity.
  • E. 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.
  • 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_69f34905e098819082191a6922a6d607 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6ba1733408190af579d93a7946508 completed May 3, 2026, 2:59 a.m.
PD Predicate disambiguation batch_69f6b3a970b0819090c6473844ffa8e3 completed May 3, 2026, 2:32 a.m.
Created at: May 1, 2026, 12:32 a.m.