https://urkesh.org/MZ/A/J01/D/F/0288.htm

Unit Book J1

Plaza adjacent the Large Temple Terrace (Version 1a)

J1f288

Processed on 2024-12-11

1. OVERVIEW

Roster Date Author Record
Equals other label 2006-10-04 lC f298 (isolated stone) [Input: V114LC.j]
Included in other label 2009-09-13 lC ^wall2 [Input: T913LC.j]
Category !! !! installation
Best definition 2008-08-16 mM wall [Input: S828RE1.j]
Summary 2009-09-11 lC Big stone wall running West to East and bonded with wall f259 forming a big structure, likely linked with a Late Chalcolithic mound and plaza. The wall is built with irregular big sized stones and smaller stones to regularize the face. The lower courses are made of bigger stones, better set out in the ground. The wall is slightly inclined to the north and it is built of a single row of stones, probably as a retaining wall. It is about two meters in height, but we don't know how its original height was because likely it was originally higher, as it seems shown by the many collapsed stones belonging to f336. The wall is poorly preserved to the west, in part probably for ancient collapse, in part for later ED III cuts that removed some of its stones. [Input: T831LC.j]
Best image 2010-08-05 lC [Input: U805LC.j]

2. IDENTIFICATION

Designation

Roster Date Author Record
Description (summary) 2008-08-28 rE This feature consists of group of stones in k128, having east-west orientation, that is, they are parallel to the wall f72. The shape of the stones look like a wall, but we are not very sure that it's a wall due to the small trench that we opened. It could be the fourth millinium wall, due to the analysing of the pottery in the features above it, Which are all LC sherds as mKB reports. Further excavation will clarify the function of f288. [Input: S813RE.j]

3. STRATIGRAPHY

Recovery/Assignment

Roster Date Author Record
Daily notes about recovery of elements 2009-08-10 lC Today we uncovered other stones of this wall running to the west. The stones are big in size, and what we assume is the face (the southern) doesn't appear very regular. Between the junctures of the stones there is a really brown and clayish material, coming perhaps from water seepage, or maybe it was a sort of packing, like for the revetment wall f72. [Input: T808LC.j]
Argument 2006-10-04 lC The band of baqaya f 342 and the deeper one (f353) show that probably the water flowing was an important problem for the structure a8. They show a later attempt to protect a8 and most of all wall f288, that probably originally didn't have any type of protection from the water, as also shown from its coarse construction and from the damage f344 (v432). [Input: V114LC.j]
2009-04-07 gB A. The interpretation of these stones as the fourth millennium revetment wall is based on the following considerations.
1. The stones are typologically similar to those of the third millennium wall revetment wall ^w2.
2. The general alignment is parallel to that of the third millennium revetment wall. This assumption is weakened by the fact that we do not have either the northern or the southern face of this presumed wall. However, the exposure is sufficient to warrant our assumption at least hypothetically.
The assumption of a wall in this position accounts well for the finding of Late Chalcolithic material immediately below the early Ninevite V material (see the reconstruction of the depositional sequence): it would have marked the base of what appears to be a Late Chalcolithc glacis located immediately below the third millennium glacis. [Input: T407GB.j]
2009-04-07 gB B. The assumption that the stones as we see them are near the bottom of the wall is more tenuous. There are two arguments in its favor.
1. The third millennium wall is too thin to be considered a retaining wall, such as would be required to withstand the pressure of a newly built glacis. For this reason we consider it a "revetment" (rather tan "retaining") wall.
2. The assumption that the glacis behind the third millennium wall is early explains better the presence of late Chalcolithic III material at a very high elevation in J3.
The alternative possibility, that the stones as we see them are near the top of the wall, would be suggested by the difficulty deriving from the fact that, were this the base of the earlier wall, most of this earlier wall would have had to be torn down when the escarpment of the third millennium was built. [Input: T407GB.j]

Volumetric Localization

Roster Date Author Record
Locus 2008-08-16 mM k128 [Input: S828RE1.j]
Relays (applicable to elements) 2008-08-26 mM r939 (41222 47330 - 8638 / Relay location: 1) [Input: S907RE-R.j]
2008-09-17 rE r967 (41146 47380 - 8578 / Relay location: SE corner) [Input: S917RE1R.j]
2008-09-17 rE r968 (41181 47398 - 8567 / Relay location: NE corner) [Input: S917RE1R.j]
2008-09-17 rE r969 (41203 47374 - 8562 / Relay location: middle) [Input: S917RE1R.j]
2008-09-17 rE r970 (41215 47378 - 8562 / Relay location: N corner) [Input: S917RE1R.j]
2008-09-17 rE r971 (41224 47355 - 8569 / Relay location: NW corner) [Input: S917RE1R.j]
M#/elev @top 2008-08-16 mM m4680 [Input: S828RE1.j]
M#/elev @bottom 2009-09-14 lC 8475 [Input: T915LC4.j]

Contact Association

Roster Date Author Record
Type of contact: latest events 2009-08-22 lC f321 (cut) cuts f288 (wall) [Input: T822LC.j]
2009-08-22 lC f329 (accumulation C) abuts f288 (wall) [Input: T822LC.j]
2009-08-22 lC f340 (accumulation) abuts f288 (wall) [Input: T822LC.j]
2009-08-22 lC f345 (accumulation C) abuts f288 (wall) [Input: T822LC.j]
2009-08-22 lC f347 (accumulation D) abuts f288 (wall) [Input: T822LC.j]
2009-08-22 lC f350 (accumulation D) abuts f288 (wall) [Input: T822LC.j]
2009-08-22 lC f355 (accumulation B) abuts f288 (wall) [Input: T822LC2.j]
2009-08-22 lC f358 (accumulation D) abuts f288 (wall) [Input: T822LC2.j]
2009-08-22 lC f359 (accumulation C) abuts f288 (wall) [Input: T822LC2.j]
2009-08-22 lC f362 (accumulation D) abuts f288 (wall) [Input: T822LC2.j]
2009-08-22 lC f363 (accumulation D) abuts f288 (wall) [Input: T822LC2.j]
2009-08-22 lC f196 (early escarpment) overlays f288 (wall) [Input: T822LC2.j]
2009-08-22 lC f341 (accumulation D) overlays f288 (wall) [Input: T822LC.j]
2009-09-11 lC f369 (accumulation D) overlays f288 (wall) [Input: T831LC.j]
Type of contact: contemporary events/movable items 2009-08-22 lC f288 (wall) bonds with f259 (wall) [Input: T822LC2.j]
Type of contact: earliest events 2009-08-22 lC f288 (wall) overlays f356 (wall) [Input: T822LC2.j]
2009-08-22 lC f288 (wall) overlays f357 (accumulation B) [Input: T822LC2.j]

Spatial Aggregation

Roster Date Author Record
Aggregate (to which element belongs) 2009-08-13 lC a8 (Stone structure) [Input: T815LC.j]

Time Sequencing

Roster Date Author Record
Stratum (to which element belongs) 2011-02-10 lC s850J1A [Input: V211LC.j]
Phase (to which element belongs) 2011-02-10 !! h2mJ1A [Input: V211LC.j]
Stratigraphic reasons of assignment 2011-02-11 lC Very deep elevation (deepest 8475), and position at the base of the Late Chalcolithic Mound, that, as shown mainly in J3, reaches a very hign elevation. The base of the wall is abutted by two features (f350 and ff355) intepreted as Late Chalcolithic on the bases of few pottery sherds. [Input: V212LC.j]
Other reasons, reservations, qualifications 2012-10-15 lC As for f259 the date is uncertain, first assigned to late Chalcolithic on the base of the few sherds found at the bottom of it, then has been suggested a Ninevite 5 date, on the basis of stratigraphic relationship with the nearby units. Following a conservative intepretation we assign it to phase 3f-JPD, waiting for new excavation for a final assignement. For a more detailed discussion see topic "LC or Ninevite structure?" [Input: V928LC.j]

4. TYPOLOGY

Morphology

Roster Date Author Record
Color 2008-08-16 mM very pale gray [Input: S828RE1.j]

6. REFERENCE

Analogical Record

Roster Date Author Record
View/drawing of features

2008-08-25 rE [Input: SZ23RE.j]

2008-08-26 rE [Input: SZ23RE.j]

2008-08-26 rE [Input: SZ23RE.j]

2008-08-26 rE [Input: SZ23RE.j]

2008-08-27 rE [Input: SZ23RE.j]

2008-08-27 rE [Input: SZ23RE.j]

2008-08-27 rE [Input: SZ23RE.j]

2008-08-27 rE [Input: SZ23RE.j]

2009-07-19 lC [Input: T729LC.j]

2009-07-21 lC [Input: T729LC.j]

2009-07-27 lC [Input: T819MM3.j]

2009-07-27 lC [Input: T819MM3.j]

2009-07-28 lC [Input: T819MM3.j]

2009-07-28 lC [Input: T819MM3.j]

2009-08-03 mM [Input: T902LC.j]

2009-08-05 lC [Input: T902LC.j]

2009-08-09 lC [Input: T909LC.j]

2009-08-09 lC [Input: T909LC.j]

2009-08-10 lC [Input: T909LC.j]

2009-08-10 lC [Input: T909LC.j]

2009-08-11 lC [Input: T909LC.j]

2009-08-11 lC [Input: T909LC.j]

2009-08-12 lC [Input: T823LC2.j]

2009-08-12 lC [Input: T823LC2.j]

2009-08-12 lC [Input: T823LC2.j]

2009-08-12 lC [Input: T823LC2.j]

2009-08-12 lC [Input: T823LC2.j]

2009-08-12 lC [Input: T823LC2.j]

2009-08-13 lC [Input: T823LC2.j]

2009-08-13 lC [Input: T823LC2.j]

2009-08-13 lC [Input: T823LC2.j]

2009-08-13 lC [Input: T823LC2.j]

2009-08-13 lC [Input: T823LC2.j]

2009-08-13 lC [Input: T823LC2.j]

2009-08-15 lC [Input: T823LC2.j]

2009-08-15 lC [Input: T824LC.j]

2009-08-15 lC [Input: T824LC.j]

2009-08-15 lC [Input: T824LC.j]

2009-08-15 lC [Input: T824LC.j]

2009-08-15 lC [Input: T824LC.j]

2009-08-15 lC [Input: T824LC.j]

2009-08-16 lC [Input: T824LC.j]

2009-08-17 lC [Input: T824LC.j]

2009-08-17 lC [Input: T824LC.j]

2009-08-17 lC [Input: T824LC.j]

2009-08-17 lC [Input: T824LC.j]

2009-08-17 lC [Input: T824LC.j]

2009-08-17 lC [Input: T824LC.j]

2009-08-18 lC [Input: T824LC.j]

2009-08-18 lC [Input: T824LC.j]

2009-08-18 lC [Input: T824LC.j]

2009-08-18 lC [Input: T824LC.j]

2009-08-26 lC [Input: T902LC.j]

2009-08-26 lC [Input: T902LC.j]

2009-08-27 lC [Input: T902LC.j]

2009-08-27 lC [Input: T902LC.j]

2009-08-27 lC [Input: T902LC.j]

2009-08-27 lC [Input: T902LC.j]

2009-08-27 lC [Input: T902LC.j]

2009-08-27 lC [Input: T902LC.j]

2009-08-27 lC [Input: T902LC.j]

2009-08-27 lC [Input: T902LC.j]

2009-08-27 lC [Input: T902LC.j]

2009-08-27 lC [Input: T902LC.j]

2009-08-27 lC [Input: T902LC.j]

2009-08-27 lC [Input: T902LC.j]

2009-09-01 lC [Input: T902LC.j]

2009-09-01 lC [Input: T902LC.j]

2009-09-01 lC [Input: T902LC.j]

2009-09-01 lC [Input: T902LC.j]

2009-09-01 lC [Input: T902LC.j]

2009-09-01 lC [Input: T902LC.j]

2009-09-01 lC [Input: T902LC.j]

2009-09-01 lC [Input: T902LC.j]

2009-09-01 lC [Input: T902LC.j]

2009-09-01 lC [Input: T902LC.j]