Who named Beersheba?

What follows is one scholar’s way of reading this disagreement — a critical-historical view that often concludes the texts genuinely disagree. It draws on the peer-reviewed sources listed below and stands as one position among the answers above, presented for transparency, not as GEBible’s position.

How critical scholarship weighs this: Widely regarded as a genuine contradiction

This summarizes where critical scholarship tends to land on this tension — a report on the field’s center of gravity, not GEBible’s own ruling.

Genesis 21:31 reports that Abraham named the place Beersheba (*bĕʾēr šebaʿ*) after he and Abimelech swore an oath there over a disputed well: "wherefore he called that place Beersheba, because there they sware both of them." Genesis 26:33 attributes the naming to Isaac, who, after his servants find water and after his own oath-treaty with Abimelech, calls the well Shibah, "therefore the name of the city is Beersheba unto this day." Both passages exploit the same Hebrew wordplay — *šebaʿ* ("seven") and *šĕbuʿāh* ("oath") — and both use etiological-origin language presenting their account as *the* explanation for the toponym.

The harmonizing reading offered by Hamilton and Waltke is a re-naming/re-digging scenario: Isaac, returning to his father's territory, re-opens wells Abraham had dug, which the Philistines had stopped up — a detail Genesis 26:18 states explicitly ("Isaac digged again the wells of water, which they had digged in the days of Abraham his father") — and ceremonially re-applies the name his father had given. As narrative logic this is workable, and it deserves to be granted: sites were renamed and names reaffirmed across generations, and 26:18 shows the text is conscious of Isaac retracing Abraham's steps. One can therefore reconcile the two scenes as two distinct events at a single location, the later one reactivating an inherited name.

The difficulty is that the re-naming reading sits awkwardly with how strongly each account presents itself as the *first* and definitive etiology. Genesis 26:33's "therefore the name of the city is Beersheba unto this day" is the standard formula for an origin explanation, not a re-confirmation, and 21:31 is equally an origin statement. More telling is the density of parallels surrounding the two naming scenes. The wife-sister deception recurs three times in Genesis — Abraham and Sarah before Pharaoh (12), Abraham and Sarah before Abimelech of Gerar (20), and Isaac and Rebekah before Abimelech of Gerar (26). Both Abraham (21:22, 32) and Isaac (26:26) treat with an Abimelech whose military commander is named Phicol. Both dig or contest wells in the Gerar–Beersheba region and conclude with an oath-treaty. The Beersheba etiology is embedded within a larger web of patriarchal doublets, not isolated.

From Hermann Gunkel onward, critical scholarship has read these as variant tellings of shared traditional legends (*Sagen*) that circulated orally and became attached to more than one patriarch, then were preserved side by side when the written sources were combined. Richard Friedman and Joel Baden assign the Abraham and Isaac material to overlapping J and E strands, with the redactor retaining both etiologies rather than collapsing them. Ronald Hendel, in *Remembering Abraham*, frames this as the characteristic behavior of cultural memory, where the same narrative motif clusters around multiple ancestral figures and is repeatedly re-anchored to prominent sites. The recurrence of an Abimelech and a Phicol across two generations, the duplicate wife-sister motif, and the duplicate Beersheba etiology together constitute a classic doublet pattern — precisely the data the Documentary Hypothesis was formulated to explain. That Abimelech is a Philistine king is itself anachronistic for the patriarchal period, since the Philistines arrive in Canaan only in the early Iron Age (c. twelfth century BCE), a sign that the stories were shaped well after the events they purport to narrate.

The re-naming harmonization is therefore genuinely *possible*: one can posit two distinct historical episodes, separated by a generation, at the same well, with kings and commanders bearing the same names, each producing the same wordplay-name. But the explanatory cost is high — it requires an improbable accumulation of coincidence and must read both etiological formulas as something other than what they say. The source-critical account explains the whole cluster economically as variant traditions preserved together. Parsimony favors the latter.

Where the critical reading lands: harmonizable at the narrative level by stacking improbable coincidences, but the doublet pattern makes a single tradition told of two patriarchs the better explanation.