27.03.2013 Views

Chapter 18 Lexical Functions: Description of Lexical Relations in a ...

Chapter 18 Lexical Functions: Description of Lexical Relations in a ...

Chapter 18 Lexical Functions: Description of Lexical Relations in a ...

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.

—<strong>Chapter</strong> <strong>18</strong>. <strong>Lexical</strong> <strong>Functions</strong>— 80<br />

ATTACKII ≈ (verbal aggression), as <strong>in</strong> Their troops launched a large-scale attack on the liberated<br />

area vs. The committee launched a scath<strong>in</strong>g attack on the Medical Research Council. (The<br />

adjectives devastat<strong>in</strong>g and violent can apply to both ATTACKI and ATTACKII; for a more<br />

precise description <strong>of</strong> the lexical cooccurrence, further senses should be dist<strong>in</strong>guished—thus,<br />

under ATTACKI one has to isolate (military operation) vs. (physical aggression) etc.<br />

— Give a KISS vs. blow a KISS: here we also have two different noun lexemes: KISS1 (X’s ges-<br />

ture <strong>of</strong> affection toward Y done with X’s lips touch<strong>in</strong>g Y’s body ...) vs. KISS2 (X’s gesture <strong>of</strong> af-<br />

fection toward Y done at a distance: X kisses X’s own f<strong>in</strong>gers and shows them to Y as if X were<br />

throw<strong>in</strong>g X’s kiss1 to Y). Then give = Oper 1(kiss1 N ) and blow = Oper 1(kiss2N). Cf. <strong>in</strong> German:<br />

e<strong>in</strong>en KUSS (kiss1) geben (give) vs. e<strong>in</strong>e KUSSHAND (kiss2) zuwerfen (throw at).<br />

— Give a LOOK vs. have a LOOK (from Cattell 1984: 84-86):<br />

(15) a. John gave 〈*had at〉 Sue a look, as if he wanted to kill her 〈... *to see what color her<br />

eyes were〉.<br />

b. John had 〈*gave〉 a look at Sue to see what color her eyes were 〈... *as if he wanted to<br />

kill her〉.<br />

c. give [N] 〈*have [at N]〉 a blank look.<br />

Here, too, we have two noun lexemes: LOOK1, which is given to express or communicate some-<br />

th<strong>in</strong>g, and LOOK2, which is had to see or learn someth<strong>in</strong>g.<br />

6.1.2 Semantic Subtypes <strong>of</strong> <strong>Lexical</strong> <strong>Functions</strong><br />

Another source <strong>of</strong> non-synonymy <strong>of</strong> the elements <strong>in</strong> the value f(L) is the existence <strong>of</strong><br />

semantic subtypes for several LFs. These subtypes are marked by way <strong>of</strong> superscripts.<br />

• For fulfillment verbs (Real, Fact, and Labreal), numerical Roman superscripts ‘ I ’, ‘ II ’, and<br />

‘ III ’ <strong>in</strong>dicate the degree <strong>of</strong> realization <strong>of</strong> the ‘requirement’ <strong>in</strong> question. Thus, Real I 1(<strong>in</strong>vitation)=<br />

accept, while Labreal II 12(<strong>in</strong>vitation) = take [NY] up [on NY’s <strong>in</strong>vitation]; <strong>in</strong> po<strong>in</strong>t <strong>of</strong> fact, you have<br />

first to accept an <strong>in</strong>vitation, and then you do whatever you are <strong>in</strong>vited to do (if noth<strong>in</strong>g <strong>in</strong>terferes<br />

<strong>of</strong> course). Cf. as well Real I<br />

3(suggestion) = accept, while Real II<br />

3(suggestion) = act [on the sug-<br />

gestion]; Real I<br />

3(advice) = accept, take and Real II<br />

3(advice) = follow; etc.<br />

The superscript ‘ I ’ denotes the m<strong>in</strong>imal degree <strong>of</strong> realization (say, at the mental level only),<br />

the superscript ‘ II ’, the middle degree <strong>of</strong> realization (the f<strong>in</strong>al degree at the mental level or the<br />

<strong>in</strong>itial degree at the physical level), and the superscript ‘ III ’, the maximal degree <strong>of</strong> realization (at<br />

the physical level).

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

Saved successfully!

Ooh no, something went wrong!