Triple
T24668299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2011 Joplin tornado |
E610747
|
entity |
| Predicate | maximumWindSpeed |
P141889
|
FINISHED |
| Object | over 200 mph |
—
|
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: over 200 mph | Statement: [2011 Joplin tornado, maximumWindSpeed, over 200 mph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumWindSpeed Context triple: [2011 Joplin tornado, maximumWindSpeed, over 200 mph]
-
A.
maximumSustainedWinds
Indicates the highest wind speed that is maintained continuously over a specified averaging period, rather than in brief gusts.
-
B.
maximumGusts
Indicates the relationship where a recorded wind gust value represents the highest (maximum) gust observed within a specified time or context.
-
C.
windSpeedPeak
chosen
Indicates the maximum wind speed reached during a specified time period or event.
-
D.
windSpeed
Indicates the measured or estimated rate at which wind is moving at a given location and time.
-
E.
windSpeedRecordDate
Indicates the date on which a particular wind speed measurement or record was observed or recorded.
- 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_69e2c4d505cc8190981881df06c0bf52 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:41 a.m.