2009 Fort Totten crash
E231160
The 2009 Fort Totten crash was a deadly rear-end collision between two Washington Metro trains on the Red Line in Washington, D.C., that became the system’s worst accident and prompted major safety reforms.
All labels observed (1)
| Label | Occurrences |
|---|---|
| 2009 Fort Totten crash canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T2090262 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 2009 Fort Totten crash Context triple: [Washington Metro Red Line, safetyIncident, 2009 Fort Totten crash]
-
A.
2020 Calabasas helicopter crash
The 2020 Calabasas helicopter crash was a fatal accident in Southern California that killed basketball legend Kobe Bryant, his daughter Gianna, and seven others, prompting widespread global mourning and scrutiny of helicopter safety practices.
-
B.
US Airways Flight 1549
US Airways Flight 1549 was the 2009 passenger flight that famously ditched in the Hudson River after a bird strike disabled both engines, with all 155 people on board surviving.
-
C.
American Airlines Flight 77
American Airlines Flight 77 was the hijacked domestic passenger flight that was crashed into the Pentagon during the September 11, 2001 terrorist attacks.
-
D.
United Airlines Flight 93
United Airlines Flight 93 was a hijacked passenger flight during the September 11, 2001 terrorist attacks that crashed in Pennsylvania after passengers attempted to overpower the hijackers.
-
E.
Alaska Airlines Flight 261
Alaska Airlines Flight 261 was a scheduled passenger flight that tragically crashed into the Pacific Ocean in 2000 after a catastrophic mechanical failure, killing all 88 people on board and prompting major safety investigations and reforms.
- 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: 2009 Fort Totten crash Target entity description: The 2009 Fort Totten crash was a deadly rear-end collision between two Washington Metro trains on the Red Line in Washington, D.C., that became the system’s worst accident and prompted major safety reforms.
-
A.
2020 Calabasas helicopter crash
The 2020 Calabasas helicopter crash was a fatal accident in Southern California that killed basketball legend Kobe Bryant, his daughter Gianna, and seven others, prompting widespread global mourning and scrutiny of helicopter safety practices.
-
B.
US Airways Flight 1549
US Airways Flight 1549 was the 2009 passenger flight that famously ditched in the Hudson River after a bird strike disabled both engines, with all 155 people on board surviving.
-
C.
American Airlines Flight 77
American Airlines Flight 77 was the hijacked domestic passenger flight that was crashed into the Pentagon during the September 11, 2001 terrorist attacks.
-
D.
United Airlines Flight 93
United Airlines Flight 93 was a hijacked passenger flight during the September 11, 2001 terrorist attacks that crashed in Pennsylvania after passengers attempted to overpower the hijackers.
-
E.
Alaska Airlines Flight 261
Alaska Airlines Flight 261 was a scheduled passenger flight that tragically crashed into the Pacific Ocean in 2000 after a catastrophic mechanical failure, killing all 88 people on board and prompting major safety investigations and reforms.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
rail accident
ⓘ
train collision ⓘ transport disaster in the United States ⓘ |
| cause |
failure of automatic train control system to detect stopped train
ⓘ
insufficient safety oversight ⓘ track circuit malfunction ⓘ |
| collisionType | rear-end collision ⓘ |
| country | United States of America ⓘ |
| date | 2009-06-22 ⓘ |
| emergencyResponseBy | District of Columbia Fire and Emergency Medical Services Department ⓘ |
| fatalities | 9 ⓘ |
| followingTrainStatus | operating in automatic mode ⓘ |
| governmentResponse | congressional hearings on transit safety ⓘ |
| hasShortName |
2009 Washington Metro train collision
ⓘ
Fort Totten Metro crash ⓘ |
| injuries | 70+ ⓘ |
| investigatedBy | National Transportation Safety Board ⓘ |
| involvedRollingStockSeries | 1000-series railcars ⓘ |
| jurisdiction | District of Columbia ⓘ |
| leadingTrainStatus | stopped on track ⓘ |
| ledTo |
public scrutiny of Washington Metro maintenance practices
ⓘ
review of automatic train operation policies ⓘ |
| legacy | catalyst for long-term safety culture changes at Washington Metro ⓘ |
| lineSegment | between Takoma and Fort Totten stations ⓘ |
| location |
Fort Totten station
ⓘ
Washington, D.C. ⓘ |
| mediaCoverage | extensive national news coverage in the United States ⓘ |
| notableFor | deadliest accident in Washington Metro history ⓘ |
| numberOfTrainsInvolved | 2 ⓘ |
| operator | Washington Metropolitan Area Transit Authority ⓘ |
| partOf | history of the Washington Metro ⓘ |
| precededBy | earlier non-fatal signal and track circuit issues on Washington Metro ⓘ |
| prompted |
increased federal oversight of transit safety
ⓘ
major safety reforms at Washington Metro ⓘ recommendations to phase out 1000-series cars ⓘ |
| railwayAccidentCategory | urban rail accident ⓘ |
| railwayAccidentClass | signal system failure-related accident ⓘ |
| railwayLine |
Washington Metro Red Line
ⓘ
surface form:
Red Line (Washington Metro)
|
| railwaySystem | Washington Metro ⓘ |
| reportPublishedBy | National Transportation Safety Board ⓘ |
| safetyOutcome |
changes to automatic train control procedures
ⓘ
enhanced track circuit testing requirements ⓘ greater emphasis on manual operation during anomalies ⓘ |
| timeOfDay | evening rush hour ⓘ |
| trainType | rapid transit train ⓘ |
| victimCountCategory | mass-casualty incident ⓘ |
| worstAccidentOfSystem | Washington Metro ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: 2009 Fort Totten crash Description of subject: The 2009 Fort Totten crash was a deadly rear-end collision between two Washington Metro trains on the Red Line in Washington, D.C., that became the system’s worst accident and prompted major safety reforms.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.