Ninurta-nadin-shumi

king of Babylon
Person human Q2997561
Press Enter · cited answer in seconds

Ninurta-nadin-shumi

Summary

Ninurta-nadin-shumi is a human[1]. He was born on -1200-00-00T00:00:00Z[2]. He died on -1200-00-00T00:00:00Z[3]. He worked as a sovereign[4]. He ranks in the top 0.73% of human entities by monthly Wikipedia readership (21 views/month, #7,281 of 1,000,298).[5]

Key Facts

  • Ninurta-nadin-shumi was born on -1200-00-00T00:00:00Z[2].
  • Ninurta-nadin-shumi died on -1200-00-00T00:00:00Z[3].
  • A child of Ninurta-nadin-shumi was Marduk-nadin-ahhe[6].
  • A child of Ninurta-nadin-shumi was Nebuchadnezzar I[7].
  • Ninurta-nadin-shumi held citizenship in Babylon[8].
  • Ninurta-nadin-shumi's professions included sovereign[4].
  • Ninurta-nadin-shumi held the position of King of Babylon[9].
  • Ninurta-nadin-shumi's image is recorded as Ninurta-nadin-shumi in Akkadian.png[10].
  • Ninurta-nadin-shumi is recorded as male[11].
  • Ninurta-nadin-shumi's instance of is recorded as human[12].
  • Ninurta-nadin-shumi's Freebase ID is recorded as /m/0hqz_mh[13].
  • Ninurta-nadin-shumi's Rodovid ID is recorded as 839948[14].

Body

Origins and Family

Ninurta-nadin-shumi was born on -1200-00-00T00:00:00Z[2].

Career and Affiliations

Ninurta-nadin-shumi worked as a sovereign[4]. He held the position of King of Babylon[9].

Personal Life

Children include Marduk-nadin-ahhe[6], a sovereign[15], b. -1150[16], of Babylon[17] and Nebuchadnezzar I[7], a sovereign[18], -1200–-1104[19], of Babylonia[20].

Death and Burial

Ninurta-nadin-shumi died on -1200-00-00T00:00:00Z[3].

Why It Matters

Ninurta-nadin-shumi ranks in the top 0.73% of human entities by monthly Wikipedia readership (21 views/month, #7,281 of 1,000,298).[5] He has Wikipedia articles in 12 language editions, a strong signal of global cultural recognition.[21] He is known by 4 alternative names across languages and contexts.[22]

FAQs

What did Ninurta-nadin-shumi do for work?

Ninurta-nadin-shumi worked as sovereign[4].

References

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

Direct Wikidata claims

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

Inline context (facts about related entities)

  1. [15] . Wikidata. wikidata.org. → on this site
  2. [16] . Wikidata. wikidata.org. → on this site
  3. [17] . Wikidata. wikidata.org. → on this site
  4. [18] . Wikidata. wikidata.org. → on this site
  5. [19] . Wikidata. wikidata.org. → on this site
  6. [20] . Wikidata. wikidata.org. → on this site

Class ancestry

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

Aggregate / graph-position facts

  1. [5] . Wikimedia Foundation. dumps.wikimedia.org.
  2. [21] . Wikidata sitelinks. wikidata.org.
  3. [22] . 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). Ninurta-nadin-shumi. Retrieved April 10, 2026, from https://4ort.xyz/entity/ninurta-nadin-shumi
MLA “Ninurta-nadin-shumi.” 4ort.xyz Knowledge Graph, 4ort.xyz, 10 Apr. 2026, https://4ort.xyz/entity/ninurta-nadin-shumi.
BibTeX @misc{4ortxyz_ninurta-nadin-shumi_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{Ninurta-nadin-shumi}}, year = {2026}, url = {https://4ort.xyz/entity/ninurta-nadin-shumi}, note = {Accessed: 2026-04-10}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): Ninurta-nadin-shumi — https://4ort.xyz/entity/ninurta-nadin-shumi (retrieved 2026-04-10)

Canonical URL: https://4ort.xyz/entity/ninurta-nadin-shumi · Last refreshed: