Triple

T23272148
Position Surface form Disambiguated ID Type / Status
Subject Rolling Fork, Mississippi E588316 entity
Predicate impactOf2023Tornado P124172 FINISHED
Object widespread destruction of homes and businesses 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: widespread destruction of homes and businesses | Statement: [Rolling Fork, Mississippi, impactOf2023Tornado, widespread destruction of homes and businesses]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: impactOf2023Tornado
Context triple: [Rolling Fork, Mississippi, impactOf2023Tornado, widespread destruction of homes and businesses]
  • A. tornado2011Description
    Indicates that the entity provides a textual description or summary of the 2011 tornado event.
  • B. impactOfDisasters chosen
    Indicates the effects or consequences that disasters have on entities, conditions, or outcomes.
  • C. tornadoIntensity2011
    Indicates the intensity level associated with a tornado event that occurred in 2011.
  • D. consequenceOf2010Disaster
    Indicates that something occurs as a result of, or is causally linked to, the 2010 disaster.
  • E. Tornado ECR
    Indicates that an entity is involved in an Engineering Change Request (ECR) specifically related to a tornado event, condition, or impact.
  • 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_69e25d148adc819088efbf42672604e9 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1957518f88190bdd88ccc4e295668 completed April 29, 2026, 5:21 a.m.
PD Predicate disambiguation batch_69effcecabd88190856fb6e1d993e4dd completed April 28, 2026, 12:18 a.m.
Created at: April 17, 2026, 4:47 p.m.