The Category P Features, Projections, Interpretation

The Category P Features, Projections, Interpretation The Category P Features, Projections, Interpretation

12.09.2014 Views

59 b. dan sam/maca et ha-sefer *al/be-megira Dan put/found Acc the-book on/in-drawer (28) a. dan ma’amin *al/be-šulxanot Dan believes on/in-tables b. dan somex al/*be-megirot Dan relies on/in-drawers Since the bottom-up dependency is associated with the locative relation, the fact that PP-verbs do not show it indicates that no such relation exists in the discussed constructions, thereby supporting the proposal that the function of P is P C , rather than P R . (iii) A locative PP can be replaced by a locative pronoun such as here/there (29a) or by a locative wh-phrase such as where (29b). Neither of these options is grammatical in (30) where the same P-morpheme (in) occurs with a PP-verb: (29) a. Dan sleeps in the garden/here. b. Where does Dan sleep? (30) a. Dan believes in love/*here. b.*Where does Dan believe? (iv) PP-verb constructions (31a) contrast sharply with locative constructions (31b) with respect to binding (Hestvik 1991, Reinhart and Reuland 1993). In the latter a pronoun coindexed with the subject is grammatical, whereas in the former a reflexive must be used; using a pronoun results in ungrammaticality. (31) a. dan i somex *al-av i /al acmo i Dan i relies on-him/on himself b. dan i sam et ha-kova al-av i /??al acmo i Dan put Acc the-hat on-him/on himself Under the approach to Binding developed in Reinhart and Reuland 1993 (“Reflexivity”, henceforth), the obligatoriness of the reflexive and the impossibility of the pronoun in (31a) indicate that the preposition of PP-verbs is not a predicate. In the

60 theory of P developed in chapter 2 this amounts to identifying this P as P C , rather than as P R (see chapter 4 for a more extensive discussion of the notion predicate under “Reflexivity” framework). To recapitulate, the preposition in PP-verb constructions does not denote the locative relation (or any relation, for that matter), indicating that it is P C rather than P R . The function of P C is to check the Case feature of the nominal. Thus, P C does not contribute to the meaning of a verb, but rather is consistent with (one of) its meaning(s). In this respect, recall that there are few PP-verbs such as ba’at (‘kicked’), which realize their internal argument either as a DP or as a PP ((17) repeated below as (32)). (32) a. dan ba’at et ha-kadur Dan kicked Acc the-ball b. dan ba’at ba-kadur Dan kicked in+the-ball The view of P C argued for above implies that such verbs are listed twice, that is ba’at (‘kicked’) in (32a) and ba’at (‘kicked in’) in (32b) are separate lexical entries. The double listing might seem not very elegant, or even counter-explanatory, as it implies that there is no systematic connection between the verbal entries. In fact, this is indeed the case. Although both entries share the core lexical meaning, the relation between them is not systematic, at least not in the relevant sense (e.g. active-passive; transitive-unaccusative/middle/reflexive). Furthermore, since the number of the ambiguous verbs that give rise to the DP/PP alternation is very small (I know of 5 altogether), the double listing cannot be argued to enlarge the lexicon in any problematic way. 3.3.2 P C is a syntactic head Until now I have been assuming, without any support, that the prepositions in PP-verb constructions are syntactic heads that combine with the following DP and project a PP, as schematicized in (33): 25 25 Based on its classification as a functional head (see 2.1), I assume that P merges its complement in the same fashion as the other functional heads (C, T, D). For another view, see Kayne (1994, 2001, 2002).

60<br />

theory of P developed in chapter 2 this amounts to identifying this P as P C , rather than<br />

as P R (see chapter 4 for a more extensive discussion of the notion predicate under<br />

“Reflexivity” framework).<br />

To recapitulate, the preposition in PP-verb constructions does not denote the<br />

locative relation (or any relation, for that matter), indicating that it is P C rather than<br />

P R . <strong>The</strong> function of P C is to check the Case feature of the nominal. Thus, P C does not<br />

contribute to the meaning of a verb, but rather is consistent with (one of) its<br />

meaning(s). In this respect, recall that there are few PP-verbs such as ba’at (‘kicked’),<br />

which realize their internal argument either as a DP or as a PP ((17) repeated below as<br />

(32)).<br />

(32) a. dan ba’at et ha-kadur<br />

Dan kicked Acc the-ball<br />

b. dan ba’at ba-kadur<br />

Dan kicked in+the-ball<br />

<strong>The</strong> view of P C argued for above implies that such verbs are listed twice, that is<br />

ba’at (‘kicked’) in (32a) and ba’at (‘kicked in’) in (32b) are separate lexical entries.<br />

<strong>The</strong> double listing might seem not very elegant, or even counter-explanatory, as it<br />

implies that there is no systematic connection between the verbal entries. In fact, this<br />

is indeed the case. Although both entries share the core lexical meaning, the relation<br />

between them is not systematic, at least not in the relevant sense (e.g. active-passive;<br />

transitive-unaccusative/middle/reflexive). Furthermore, since the number of the<br />

ambiguous verbs that give rise to the DP/PP alternation is very small (I know of 5<br />

altogether), the double listing cannot be argued to enlarge the lexicon in any<br />

problematic way.<br />

3.3.2 P C is a syntactic head<br />

Until now I have been assuming, without any support, that the prepositions in<br />

PP-verb constructions are syntactic heads that combine with the following DP and<br />

project a PP, as schematicized in (33): 25<br />

25 Based on its classification as a functional head (see 2.1), I assume that P merges its complement in<br />

the same fashion as the other functional heads (C, T, D). For another view, see Kayne (1994, 2001,<br />

2002).

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

Saved successfully!

Ooh no, something went wrong!