Triple
T32673240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Mississippi Flood of 1927 |
E835353
|
entity |
| Predicate | areaFlooded |
P144026
|
FINISHED |
| Object | approximately 27,000 square miles |
—
|
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: approximately 27,000 square miles | Statement: [Great Mississippi Flood of 1927, areaFlooded, approximately 27,000 square miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areaFlooded Context triple: [Great Mississippi Flood of 1927, areaFlooded, approximately 27,000 square miles]
-
A.
inundatedRegion
Indicates that a region is covered or overwhelmed by water, typically due to flooding or heavy precipitation.
-
B.
floodLocation
chosen
Indicates that a flooding event occurs at, affects, or is situated in a specified location.
-
C.
floodedFor
Indicates that one entity is intentionally inundated or submerged with water (or another liquid) for the benefit, use, or purpose of another entity.
-
D.
hasFloodRiskAreas
Indicates that certain areas are subject to potential flooding or are classified as being at risk of flood events.
-
E.
drainageAreaApprox
Indicates that one entity has an approximate drainage area measured or characterized by the other entity.
- 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_69f3493134b48190aa3c8cb523bd3800 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c7aed2888190ac2feb5f1a80ef43 |
completed | May 3, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:09 a.m.