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.

2.7 The link between the BNBV construction and the rise of ergativity<br />

There are, in my view, two possible analyses of a BNBV construction: these two<br />

structures seem to correspond to the alienability of the absolutive noun that forms a<br />

component of the compound verb and they may also correspond to two distinct phases in<br />

the history of the development of ergativity in Sumerian. The older of these two<br />

structures, which corresponds to BNBV constructions in which the nominal component is<br />

inalienable, is analogous to an English existential sentence in which the post-copular<br />

noun is modified by a secondary/adjectival predicate.<br />

(101) [ ∃ (en aratta ki .ke 4) gig.e igi √du 8] √bi<br />

There is [ ∃ an eye (of the Lord of Aratta) opened up on the wheat]<br />

Within the structure outlined in (101), the ergative case-marked noun is the inalienable<br />

possessor of igi and is non-agentive, while the apparent main verb, √du 8, is actually an<br />

adjective modifying igi just as secondary predicates typically modify the direct object in<br />

secondary predicate environments. The actual main verb in such a construction is the<br />

verbal prefix *bi-√. As Pylkkänen predicted for low applicative morphemes, the low<br />

applicative takes three arguments: the lexical verb (√du 8), the direct object (igi) and the<br />

indirect object (gig.e).<br />

In contrast, the second of the two structures, in which the nominal component of the<br />

compound verb is alienable, would have resulted from the grammaticalization of the<br />

possessive construction as a new ergative construction (Trask 1979; see below, chapter 5,<br />

188

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

Saved successfully!

Ooh no, something went wrong!