Triple
T33439343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1993 Midwest floods |
E856316
|
entity |
| Predicate | highestFloodStageLocation |
P72076
|
FINISHED |
| Object | St. Louis, Missouri |
—
|
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: St. Louis, Missouri | Statement: [1993 Midwest floods, highestFloodStageLocation, St. Louis, Missouri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestFloodStageLocation Context triple: [1993 Midwest floods, highestFloodStageLocation, St. Louis, Missouri]
-
A.
floodPeakLocation
chosen
Indicates the location at which the maximum intensity or highest level of a flood event occurs.
-
B.
floodStage
Indicates that a water body’s level has reached or exceeded the defined height at which flooding is expected to begin or become hazardous.
-
C.
floodLocation
Indicates that a flooding event occurs at, affects, or is situated in a specified location.
-
D.
floodHeight
Indicates the measured vertical level or depth reached by floodwaters at a specific location or time.
-
E.
waterLevelHighestIn
Indicates that the referenced location or container has the greatest water level compared to a specified set of locations or containers.
- 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 1, 2026, 1:37 a.m.