06.04.2013 Views

Johnson 2004 - CDLI - UCLA

Johnson 2004 - CDLI - UCLA

Johnson 2004 - CDLI - UCLA

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Gragg’s statistics, based on a corpus of Old Babylonian materials from Nippur is equally<br />

convincing (note that some of Gragg’s numbers are approximate).<br />

Postposition Infix Co-occurrences<br />

-ße 3 / -ßi- 700 142 35<br />

-ta / -ta- 380 100 29<br />

-da / -da- 170 430 26<br />

Gragg emphasizes that, with the exception of clauses that include a verb of motion, the<br />

postposition and its etymologically corresponding infix almost never occur in the same<br />

clause.<br />

Although further research into the distribution of postpositions and their<br />

etymologically related infixes is needed, I would guess that, excluding verbs of motion,<br />

the postposition regularly occurs with definite lexical noun phrases, the infix when the<br />

lexical noun is pronominalized and the *bi-√ prefix when the relevant adverbial argument<br />

is indefinite. This would make the *bi-√ prefix the unmarked term in the system of<br />

dimensional infixes, a system that is organized on the basis of oppositions of source (-ta)<br />

and goal (-ße 3), which coincides with the semantic field that I would associate with the<br />

*bi-√ prefix. The plausibility of *bi-√ as the unmarked dimensional infix follows quite<br />

naturally from its role as a low source applicative when it is immediately preceded by an<br />

inalienable noun. We can presumably juxtapose the importance of the source argument in<br />

the Sumerian low source applicative in BNBV inal across a number of distinct lexical<br />

classes: (i) verbs of perception include an indefinite noun in a raised possessor<br />

construction (with the experienced object as the raised possessor of an inalienable noun<br />

84

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!