Triple
T6688118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joplin, Missouri |
E152150
|
entity |
| Predicate | tornadoDate2011 |
P69049
|
FINISHED |
| Object | May 22, 2011 |
—
|
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 22, 2011 | Statement: [Joplin, Missouri, tornadoDate2011, May 22, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tornadoDate2011 Context triple: [Joplin, Missouri, tornadoDate2011, May 22, 2011]
-
A.
tornadoSeasonPeak
Indicates the time period during which tornado activity typically reaches its highest frequency or intensity in a given region.
-
B.
dateOfLandfall
chosen
Indicates the specific calendar date on which a storm or similar event first makes landfall at a particular location.
-
C.
lastStormDissipated
Indicates that the most recent storm in a given context has ended and lost its organized structure or intensity.
-
D.
Tornado IDS
Indicates that an entity functions as an identification system specifically for tornado-related detection, tracking, or classification.
-
E.
secondMajorLandfallDate
Indicates the calendar date on which an entity, such as a storm or similar event, makes its second significant 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_69c687f9977c819097e7f5ada4fe522e |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cd0fa5188190a23281cb09d98139 |
completed | March 27, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69c6ad0d3c1081908dadff7a6a054123 |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:04 p.m.