RESEARCH / IDENTITY EVIDENCE

Names need context, not just a match.

Source-scoped comparisons distinguish text, language, original records and unresolved historical identities.

Identical spelling is not identical identity. A tablet findspot, a damaged personal name and a biblical passage have different evidentiary roles. Each reference below resolves to an existing concordance citation, not an invented identification.

8 researched cases / 12 checked source links. Scripture is primary for what its text says; historical object identities require independent material evidence. All cases remain awaiting specialist review.

PLACE / different witnesses

Aššur and Asshur in Genesis

Indexed forms: Aššur, Assur, Ashur, Asshur

Research question: Do similar names prove that a dated Assyrian archive and a Genesis passage record the same referent?

What the source supports

Middle Assyrian tablet catalogues locate documents at Aššur, while Genesis 10 contains biblical Asshur language. These witnesses have different genres, contexts and dates; the archive does not equate a named ancestor with a tablet findspot.

What remains unproved

The similarity of these Romanised spellings alone is not an historical identity argument.

Next verification

Compare original Hebrew and Akkadian forms, textual transmission and securely dated geographical studies.

Primary reading routes

KAJ 247: workers and a temple accountObject record
The catalogue supplies an Aššur archival context, not an identified biblical individual. Concordance: Aššur
Genesis 10:8-12Biblical passage
Genesis is primary for what this biblical text says, not for an excavation provenance. Concordance: Asshur in Genesis

Independent specialist review pending

PLACE / different witnesses

Nineveh in chronicle and prophecy

Indexed forms: Nineveh

Research question: Are a surviving Babylonian chronicle and biblical prophetic accounts interchangeable records?

What the source supports

The Babylonian Chronicle case and the prophecies in Nahum and Zephaniah name Nineveh. Their genres, composition histories and physical witnesses differ; the later copy date of the Chronicle is not the date of the event it recounts.

What remains unproved

Shared naming alone does not establish identical details, motives or textual chronology.

Next verification

Independently review published chronicle lines, copy chronology and the literary contexts of both prophets.

Primary reading routes

BM 21901: the Chronicle of Nineveh's fallObject record
This object is a later copy of an ancient chronicle about Nineveh. Concordance: Nineveh
Nahum 1:1Biblical passage
Nahum explicitly introduces its prophetic subject as Nineveh. Concordance: Nineveh
Zephaniah 2:13-15Biblical passage
Zephaniah supplies another distinct prophetic reference to the city. Concordance: Nineveh

Independent specialist review pending

PLACE / catalogue alias

Šibaniba and Tell Billa

Indexed forms: Šibaniba, Shibaniba, Tell Billa

Research question: What evidence currently supports using both names for this provincial archive context?

What the source supports

The cited Billa 30 tablet is attributed to an archive described using Šibaniba and Tell Billa. This is a documented catalogue association and not a comprehensive new archaeological identification.

What remains unproved

A single catalogue association cannot establish precise ancient borders, full site chronology or every variant spelling.

Next verification

Review excavation reports, findspot records, dating and historical-geographical treatments.

Primary reading routes

Billa 30: barley obligations at ShibanibaObject record
The tablet case provides the existing attributed provincial archive context. Concordance: Šibaniba (Tell Billa)

Independent specialist review pending

PERSON / single edition

Niri-šaldi in a damaged line

Indexed forms: Niri-šaldi, Niri-shaldi

Research question: Can a partly damaged personal name be matched to a second person or document?

What the source supports

The credited editor records the name in a particular obverse line of a Middle Assyrian footwear account. The archive preserves this edition-scoped reading without constructing an unsupported biography.

What remains unproved

Damage and a single local attestation do not justify a broader person identification.

Next verification

Obtain qualified collation of the damaged signs and examine independently edited parallel attestations.

Primary reading routes

MARV 10, 07: palace footwear and a hostageObject record
The named recipient occurs in the editor's cited damaged tablet line. Concordance: Niri-šaldi

Independent specialist review pending

PERSON / scripture only index

Sargon in Isaiah 20

Indexed forms: Sargon, Sargon II

Research question: What supports this ruler's identification in the existing local concordance?

What the source supports

Isaiah 20 directly names Sargon in its narrative. The concordance entry does not yet attach a specific independently edited royal-inscription line or identified physical artefact.

What remains unproved

A missing object-level link in this index says nothing about the wider existence of historical Sargon inscriptions.

Next verification

Add an independently identified royal inscription, edition citation, line number and specialist translation assessment.

Primary reading routes

Isaiah 20:1-6Biblical passage
Isaiah is the cited biblical witness, distinct from an Assyrian inscription. Concordance: Sargon II

Independent specialist review pending

PERSON / scripture only index

Hezekiah in Second Kings

Indexed forms: Hezekiah

Research question: Does the biblical account by itself establish a line-by-line match to an Assyrian royal inscription?

What the source supports

Second Kings 18 supplies the named ruler and a biblical account of conflict. No separately identified Assyrian object and edition line is attached to this specific concordance entry.

What remains unproved

Different documents require textual and chronological comparison, not an assumed word-for-word match.

Next verification

Add identified royal edition lines with stated dating, translation uncertainty and independent historical review.

Primary reading routes

2 Kings 18:13-17Biblical passage
The referenced verses are the present biblical source for this entry. Concordance: Hezekiah of Judah

Independent specialist review pending

PERSON / scripture only index

Jehu in Second Kings

Indexed forms: Jehu

Research question: Can name similarity alone identify the biblical Jehu with an object from another source?

What the source supports

Second Kings 9 provides the indexed narrative for Jehu of Israel. The term currently lacks an independently specified archaeological line or object association in this concordance.

What remains unproved

The missing link is a limitation of this local index, not a claim that no relevant external material exists.

Next verification

Examine authenticated object editions and historical chronology before publishing a direct identification.

Primary reading routes

2 Kings 9:1-13Biblical passage
This is the cited biblical passage, without a separate local object claim. Concordance: Jehu of Israel

Independent specialist review pending

PLACE / scripture only index

Samaria and multiple biblical reports

Indexed forms: Samaria

Research question: Which distinct events and passages currently support the use of Samaria as a historical place name?

What the source supports

Second Kings 17 contains separate references to Samaria, the siege narrative and later resettlement. The current concordance has no specified Assyrian tablet or object line for this place entry.

What remains unproved

Separate episodes must not be compressed into one event or used to infer unmeasured city extent and population.

Next verification

Compare dated Assyrian inscriptions and verified site evidence against the precise biblical passages.

Primary reading routes

2 Kings 17:3-6Biblical passage
This narrative concerns Samaria and its political crisis. Concordance: Samaria
2 Kings 17:24Biblical passage
This separate passage describes resettlement as recorded in Kings. Concordance: Samaria

Independent specialist review pending

Before claiming an identification

Require an accession or edition identifier, a precise passage or line, chronology, provenanced source, manuscript uncertainty and a documented specialist assessment. Until then, an apparent parallel stays a research lead. Review the evidence register and editorial policy.