Triple
T32597083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moore, Oklahoma |
E833246
|
entity |
| Predicate | tornadoEvent |
P155881
|
FINISHED |
| Object | May 3, 1999 F5 tornado |
—
|
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: May 3, 1999 F5 tornado | Statement: [Moore, Oklahoma, tornadoEvent, May 3, 1999 F5 tornado]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tornadoEvent Context triple: [Moore, Oklahoma, tornadoEvent, May 3, 1999 F5 tornado]
-
A.
majorTornadoEvent
chosen
Indicates that a tornado event is of significant intensity or impact, typically meeting defined thresholds for severity or damage.
-
B.
tornado2011Description
Indicates that the entity provides a textual description or summary of the 2011 tornado event.
-
C.
tornadoScale1997
Indicates the intensity classification of a tornado according to the 1997 tornado scale standard.
-
D.
tornadoIntensityHistory
Indicates the recorded progression of a tornado’s intensity over time.
-
E.
stormTypeAtLandfall
Indicates the classification or category of a storm at the specific time and location where it makes landfall.
- 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_69f3492ab63c8190aec24d5003b47c29 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c695d31c8190bbd496755c70c81a |
completed | May 3, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:05 a.m.