Tōkaimura criticality accident

nuclear accident
Event criticality_accident Q1377385
Tōkaimura criticality accident
ENERGY.GOV · Public Domain · Wikimedia
Press Enter · cited answer in seconds

Tōkaimura criticality accident

Summary

Tōkaimura criticality accident is a criticality accident[1]. It draws 1,795 Wikipedia views per month (criticality_accident category, ranking #1 of 2).[2]

Key Facts

  • Tōkaimura criticality accident is located in Tōkai-mura[3].
  • Tōkaimura criticality accident is in the country of Japan[4].
  • Tōkaimura criticality accident's image is recorded as HD.15.058 (11840039684).jpg[5].
  • Tōkaimura criticality accident's instance of is recorded as criticality accident[6].
  • Tōkaimura criticality accident's follows is recorded as PNC Tōkai Works fire and explosion[7].
  • Tōkaimura criticality accident's locator map image is recorded as Map, location of Tokaimura nuclear accident.tif[8].
  • Tōkaimura criticality accident's location is recorded as JCO[9].
  • Tōkaimura criticality accident's NDL Authority ID is recorded as 00974129[10].
  • Tōkaimura criticality accident's point in time is recorded as +1999-09-30T00:00:00Z[11].
  • Tōkaimura criticality accident's coordinate location is recorded as {'lat': 36.47972222222222, 'lon': 140.5536111111111}[12].
  • Tōkaimura criticality accident's Freebase ID is recorded as /m/02vmm2d[13].
  • Tōkaimura criticality accident's number of deaths is recorded as {'amount': '+2'}[14].
  • Tōkaimura criticality accident's number of injured is recorded as {'amount': '+1'}[15].
  • Tōkaimura criticality accident's Encyclopædia Universalis ID is recorded as accident-nucleaire-de-tokai-mura[16].
  • Tōkaimura criticality accident's Namuwiki ID is recorded as 도카이 촌 방사능 누출사고[17].
  • Tōkaimura criticality accident's Encyclopedia of China is recorded as 75078[18].

Why It Matters

Tōkaimura criticality accident draws 1,795 Wikipedia views per month (criticality_accident category, ranking #1 of 2).[2] It has Wikipedia articles in 15 language editions, a strong signal of global cultural recognition.[19] It is known by 8 alternative names across languages and contexts.[20]

References

Programmatic citations — every numbered marker resolves to a verifiable graph row below.

Direct Wikidata claims

  1. [4] . wikidata.org.
  2. [5] . wikidata.org.
  3. [6] . wikidata.org.
  4. [3] . wikidata.org.
  5. [7] . wikidata.org.
  6. [8] . wikidata.org.
  7. [9] . wikidata.org.
  8. [10] . wikidata.org.
  9. [11] . wikidata.org.
  10. [12] . wikidata.org.
  11. [13] . Freebase Data Dumps. wikidata.org.
  12. [14] . wikidata.org.
  13. [15] . wikidata.org.
  14. [16] . wikidata.org.
  15. [17] . wikidata.org.
  16. [18] . wikidata.org.

Class ancestry

  1. [1] . Wikidata. wikidata.org.

Aggregate / graph-position facts

  1. [2] . Wikimedia Foundation. dumps.wikimedia.org.
  2. [19] . Wikidata sitelinks. wikidata.org.
  3. [20] . Wikidata aliases. wikidata.org.

📑 Cite this page

Use these citations when quoting this entity in research, articles, AI prompts, or wherever provenance matters. We aggregate Wikidata + Wikipedia + authoritative open-data sources; the stitched, scored, cross-referenced view is what 4ort.xyz contributes.

APA 4ort.xyz Knowledge Graph. (2026). Tōkaimura criticality accident. Retrieved May 3, 2026, from https://4ort.xyz/entity/t-kaimura-criticality-accident
MLA “Tōkaimura criticality accident.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/t-kaimura-criticality-accident.
BibTeX @misc{4ortxyz_t-kaimura-criticality-accident_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{Tōkaimura criticality accident}}, year = {2026}, url = {https://4ort.xyz/entity/t-kaimura-criticality-accident}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): Tōkaimura criticality accident — https://4ort.xyz/entity/t-kaimura-criticality-accident (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/t-kaimura-criticality-accident · Last refreshed: