Triple
T27123639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moore |
E687063
|
entity |
| Predicate | hasSevereTornadoEvent |
P15089
|
FINISHED |
| Object | 1999 Bridge Creek–Moore tornado |
—
|
NE NERFINISHED |
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: 1999 Bridge Creek–Moore tornado | Statement: [Moore, hasSevereTornadoEvent, 1999 Bridge Creek–Moore tornado]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSevereTornadoEvent Context triple: [Moore, hasSevereTornadoEvent, 1999 Bridge Creek–Moore tornado]
-
A.
majorTornadoEvent
Indicates that a tornado event is of significant intensity or impact, typically meeting defined thresholds for severity or damage.
-
B.
hasSevereWeatherRisk
Indicates that an entity is exposed to or associated with a high likelihood of severe or hazardous weather conditions.
-
C.
hasDisaster
chosen
Indicates that an entity experiences, is affected by, or is associated with a disaster event.
-
D.
tornadoIntensityHistory
Indicates the recorded progression of a tornado’s intensity over time.
-
E.
hasTropicalCyclones
Indicates that the specified region or area experiences tropical cyclones as part of its typical weather or climate conditions.
- 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_69ef148c2b588190afc15b529f7af845 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: April 27, 2026, 9 a.m.