Triple
T17751618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Massachusetts |
E443126
|
entity |
| Predicate | includesEvent |
P1393
|
FINISHED |
| Object | Great Molasses Flood |
—
|
NE NERFINISHED |
How this triple was built (3 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: Great Molasses Flood | Statement: [History of Massachusetts, includesEvent, Great Molasses Flood]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Great Molasses Flood Context triple: [History of Massachusetts, includesEvent, Great Molasses Flood]
-
A.
Vanport flood of 1948
The Vanport flood of 1948 was a catastrophic Columbia River flood that destroyed the wartime housing city of Vanport, Oregon, killing at least 15 people and displacing tens of thousands, many of them Black shipyard workers and their families.
-
B.
Great Johnstown Flood of 1889
The Great Johnstown Flood of 1889 was a catastrophic dam failure–induced deluge that devastated Johnstown, Pennsylvania, killing more than 2,200 people and becoming one of the deadliest and most infamous disasters in U.S. history.
-
C.
Hartford Flood of 1936
The Hartford Flood of 1936 was a devastating spring flood that inundated Hartford, Connecticut and surrounding areas, causing widespread damage and prompting major flood-control improvements along the city’s rivers.
-
D.
1967 Fairbanks flood
The 1967 Fairbanks flood was a devastating inundation of Fairbanks, Alaska, that caused widespread damage and led to major changes in the region’s flood control and urban planning.
-
E.
Great Flood of 1879
The Great Flood of 1879 was a catastrophic inundation of the city of Szeged in Hungary that destroyed most of the town and prompted a major reconstruction.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Great Molasses Flood Target entity description: The Great Molasses Flood was a 1919 industrial disaster in Boston, Massachusetts, in which a large storage tank burst and sent a deadly wave of molasses through city streets.
-
A.
Vanport flood of 1948
The Vanport flood of 1948 was a catastrophic Columbia River flood that destroyed the wartime housing city of Vanport, Oregon, killing at least 15 people and displacing tens of thousands, many of them Black shipyard workers and their families.
-
B.
Great Johnstown Flood of 1889
The Great Johnstown Flood of 1889 was a catastrophic dam failure–induced deluge that devastated Johnstown, Pennsylvania, killing more than 2,200 people and becoming one of the deadliest and most infamous disasters in U.S. history.
-
C.
Hartford Flood of 1936
The Hartford Flood of 1936 was a devastating spring flood that inundated Hartford, Connecticut and surrounding areas, causing widespread damage and prompting major flood-control improvements along the city’s rivers.
-
D.
1967 Fairbanks flood
The 1967 Fairbanks flood was a devastating inundation of Fairbanks, Alaska, that caused widespread damage and led to major changes in the region’s flood control and urban planning.
-
E.
Great Flood of 1879
The Great Flood of 1879 was a catastrophic inundation of the city of Szeged in Hungary that destroyed most of the town and prompted a major reconstruction.
- F. None of above. chosen
Provenance (2 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4841b3ccc8190b3241b3e0fa4b2e8 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 10:10 a.m.