Triple
T12120153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amagasaki derailment |
E288671
|
entity |
| Predicate | deadliestRailAccidentInJapanSince |
P103389
|
FINISHED |
| Object |
Sakuragichō train fire
The Sakuragichō train fire was a 1951 railway disaster in Yokohama, Japan, in which an overhead wire caused a blaze that killed more than 100 passengers and led to major safety reforms on Japanese trains.
|
E962980
|
NE FINISHED |
How this triple was built (5 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: Sakuragichō train fire | Statement: [Amagasaki derailment, deadliestRailAccidentInJapanSince, Sakuragichō train fire]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sakuragichō train fire Context triple: [Amagasaki derailment, deadliestRailAccidentInJapanSince, Sakuragichō train fire]
-
A.
Amagasaki derailment
The Amagasaki derailment was a deadly 2005 train accident in Hyōgo Prefecture, Japan, in which a commuter train left the tracks and crashed into an apartment building, prompting major scrutiny of railway safety practices.
-
B.
Hibiya Incendiary Incident
The Hibiya Incendiary Incident was a 1905 anti-government riot in Tokyo sparked by public outrage over the terms of the Treaty of Portsmouth that ended the Russo-Japanese War.
-
C.
Daegu subway fire
The Daegu subway fire was a catastrophic arson attack on a South Korean metro train in 2003 that killed nearly 200 people and led to major reforms in urban rail safety.
-
D.
Nagasaki bugyō
Nagasaki bugyō were high-ranking Tokugawa shogunate officials responsible for administering the port city of Nagasaki and overseeing Japan’s tightly controlled foreign trade and relations during the Edo period.
-
E.
Isshi Incident
The Isshi Incident was a 645 CE coup d'état in Japan in which Prince Naka no Ōe and his allies assassinated the powerful statesman Soga no Iruka, leading to the downfall of the Soga clan and paving the way for major political reforms.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Sakuragichō train fire Triple: [Amagasaki derailment, deadliestRailAccidentInJapanSince, Sakuragichō train fire]
Generated description
The Sakuragichō train fire was a 1951 railway disaster in Yokohama, Japan, in which an overhead wire caused a blaze that killed more than 100 passengers and led to major safety reforms on Japanese trains.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Sakuragichō train fire Target entity description: The Sakuragichō train fire was a 1951 railway disaster in Yokohama, Japan, in which an overhead wire caused a blaze that killed more than 100 passengers and led to major safety reforms on Japanese trains.
-
A.
Amagasaki derailment
The Amagasaki derailment was a deadly 2005 train accident in Hyōgo Prefecture, Japan, in which a commuter train left the tracks and crashed into an apartment building, prompting major scrutiny of railway safety practices.
-
B.
Hibiya Incendiary Incident
The Hibiya Incendiary Incident was a 1905 anti-government riot in Tokyo sparked by public outrage over the terms of the Treaty of Portsmouth that ended the Russo-Japanese War.
-
C.
Daegu subway fire
The Daegu subway fire was a catastrophic arson attack on a South Korean metro train in 2003 that killed nearly 200 people and led to major reforms in urban rail safety.
-
D.
Nagasaki bugyō
Nagasaki bugyō were high-ranking Tokugawa shogunate officials responsible for administering the port city of Nagasaki and overseeing Japan’s tightly controlled foreign trade and relations during the Edo period.
-
E.
Isshi Incident
The Isshi Incident was a 645 CE coup d'état in Japan in which Prince Naka no Ōe and his allies assassinated the powerful statesman Soga no Iruka, leading to the downfall of the Soga clan and paving the way for major political reforms.
- F. None of above. chosen
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deadliestRailAccidentInJapanSince Context triple: [Amagasaki derailment, deadliestRailAccidentInJapanSince, Sakuragichō train fire]
-
A.
casualtiesJapan
Indicates that an event or action resulted in casualties (deaths and/or injuries) occurring in Japan.
-
B.
casualtiesJapanKilled
Indicates that the casualties were individuals from Japan who were killed.
-
C.
SeikanTunnelConnects
Indicates that the Seikan Tunnel serves as a physical connection between two geographic locations or regions.
-
D.
JapaneseCasualtiesSurvivors
Indicates the number or status of Japanese individuals who were casualties but survived an event or conflict.
-
E.
officialDeathTollReportedByJapanese
Indicates that the officially recorded number of deaths was reported by Japanese authorities or sources.
- F. None of above. chosen
Provenance (7 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_69d6ab4b5e4c81909950b17151eb0951 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9164ada5081908676bd9e5947268a |
completed | April 10, 2026, 3:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f684172c81908b77daa243dc8ed8 |
completed | May 2, 2026, 1:05 p.m. |
| NEDg | Description generation | batch_69f5fdea1afc8190b39557fdc571e300 |
completed | May 2, 2026, 1:36 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69f5fef775508190ab3be470821c5a50 |
completed | May 2, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d9150497408190921334d21503375a |
completed | April 10, 2026, 3:19 p.m. |
| PDg | Predicate description generation | batch_69d916481a008190ae66677b9e6dd961 |
completed | April 10, 2026, 3:24 p.m. |
Created at: April 8, 2026, 9:49 p.m.