Triple
T24428562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Picher, Oklahoma |
E615928
|
entity |
| Predicate | majorTornadoEvent |
P155881
|
FINISHED |
| Object | May 10, 2008 |
—
|
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 10, 2008 | Statement: [Picher, Oklahoma, majorTornadoEvent, May 10, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorTornadoEvent Context triple: [Picher, Oklahoma, majorTornadoEvent, May 10, 2008]
-
A.
tornadoScale1997
Indicates the intensity classification of a tornado according to the 1997 tornado scale standard.
-
B.
locatedInTornadoAlley
Indicates that the subject is situated within the geographic region commonly known as Tornado Alley, where tornado activity is especially frequent.
-
C.
stormTypeAtLandfall
Indicates the classification or category of a storm at the specific time and location where it makes landfall.
-
D.
strongestStorm
Indicates that one storm is the most intense or powerful compared to a set of other storms.
-
E.
regionAffectedByNamedStorms
Indicates that a geographic region is impacted or influenced by one or more specifically named storms.
- F. None of above. chosen
Provenance (4 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296a983d88190904b559694363a19 |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f2915233c48190a181c8c1924e892c |
completed | April 29, 2026, 11:16 p.m. |
Created at: April 18, 2026, 2:15 a.m.