21.04.2013 Views

Eckhard Bick - VISL

Eckhard Bick - VISL

Eckhard Bick - VISL

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.

modify a lexicon entry. Quantitative evaluation will be affected “locally”, i.e. for the<br />

valency pattern of individual lexemes (e.g. the frequency of ‘dormir’ with a direct<br />

object), not for categorical conclusions (e.g. the frequency of @ACC or as such).<br />

If valency statistics for individual lexemes is mandatory, two solutions offer<br />

themselves:<br />

(a) A qualitative valency analysis of the corpus is done first, i.e. the automatically<br />

extracted lexical valency patterns are automatically compared to those found in the<br />

lexicon, and all differences inspected manually and added to the lexicon, where they are<br />

deemed to contain “new” valency information rather than plain erroneous tagging. After<br />

this, a new, quantitative, run is performed.<br />

(b) False positive valency readings (e.g. superfluous @ACC due to a wrong <br />

mark on the main verb) - especially unambiguous false positive readings - are extremely<br />

rare due to the “negative” way a cautious CG works - it relies mostly on REMOVE<br />

rules and the correct syntactic tag will survive (alongside or instead of, for instance, a<br />

false @ACC), since there would be nothing in the syntactic context calling for its<br />

removal. False negative valency readings (e.g. no @ACC because of a lacking <br />

mark) are more common, but will often lead to the survival of a “dummy” tag (@NPHR<br />

for nominal, @ADVL for adverbial material), which is used as function labels for the<br />

top node of utterances without a verbal top node. Now, sentences containing extra<br />

dummy labels can be filtered automatically, inspected and used to correct the individual<br />

lexeme valency statistics.<br />

- 357 -

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

Saved successfully!

Ooh no, something went wrong!