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.6 BNBV inal as a particle-verb construction<br />

Up to now, I have concentrated on the semantic properties of the BNBV inal construction,<br />

particularly in terms of lexical aspect and certain interactions between lexical and<br />

grammatical aspect. Here in the penultimate section of this chapter, I describe the formal<br />

or distributional features that code the meanings suggested above. What morphosyntactic<br />

means, in other words, are used in Sumerian to code telicity and the phenomena related to<br />

it? I argue in the following that the BNBV inal construction is a particular kind of particle-<br />

verb construction (familiar from a variety of present-day European languages) and that<br />

the *bi-√ prefix is analogous to the particle in a particle verb construction and contributes<br />

telicity to the meaning of predicates in which it occurs. It has long been recognized that<br />

in English, for example, particles—prepositions that lack a nominal complement—are<br />

often used to control the telicity of verbs.<br />

(83) He hammered it Ø for three hours / *in three hours.<br />

(84) He hammered it out for three hours / in three hours.<br />

In these examples, as is standard practice, a temporal adverb can be used to differentiate a<br />

telic event from an atelic one: in (83), an atelic verb can only occur with an unbounded<br />

temporal adverb, for three hours, whereas the telic verb in (84), which is followed by the<br />

particle out, can also occur with a bounded temporal adverb, in three hours. Since<br />

Sumerian is strictly verb-final, the possibility of a particle-based system for controlling<br />

the telicity of a verb seems out of reach. But recent work on the formation of verbal<br />

176

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

Saved successfully!

Ooh no, something went wrong!