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.

For global context syntactic rules (i.e. rules containing at least one unbounded<br />

context condition), selecting is even more risky than ordinarily. For example, it is safe<br />

to assume that a direct object reading can be removed in a sentence without a transitive<br />

verb, while the "inverse", choosing the object reading in the presence of a transitive<br />

verb, is risky, rules would have to thoroughly check for other direct objects and direct<br />

object candidates, clause boundaries and the like.<br />

In the case of tag targeting rules, cautiousness is necessary because a tag-target<br />

has to cover a range of possibly quite different lexical items, whereas a word-form<br />

target is really the equivalent of a complete tag sequence, including the lexical base<br />

form tag. Since very few syntactic rules have word-form targets, the effect is only<br />

visible in the morphological rule portion, with a remove/select ratio of 1.5 for tag<br />

targeting rules as compared to one of 1.0 for morphological rules on a whole.<br />

The elevated remove/select ratio for syntactic rules (over 4) is not only due to a<br />

higher degree of "structural globality" (as addressed by the valency based uniqueness<br />

principle), but also to the grammar specific fact that clause function tags have been<br />

attached to non-finite verbs and complementiser words (relatives, interrogatives,<br />

conjunctions), in addition to these words' clause internal function tag. Since double tag<br />

targets are not allowed in syntactic SELECT rules in the available cg-compilers, such<br />

words can only be disambiguated by REMOVE rules - a SELECT rule targeted at either<br />

the internal or the external function tag would "kill" the other of the two.<br />

Apart from low error rates, Constraint Grammar parsers are famous for their processing<br />

speed. The actual speed, even when using the same compiler on the same machine, is of<br />

course dependent on both text type and grammar size. For text type, the relevant<br />

parameters are sentence length and word form ambiguity (average number of readings<br />

per word form); for grammar size, parameters are the number of rule contexts<br />

(subsuming the number of rules as well as their complexity) and the proportion of<br />

unbounded contexts. Since the parser has to apply for every word and every one of its<br />

readings all rules that target that reading, a first approximation for sentence processing<br />

time would be one of linear complexity:<br />

(3a) time ~ n * a * R<br />

where<br />

n = number of words in the sentence<br />

a = average ambiguity (number of readings per word form<br />

R = rule number constant, depending on, but less than proportional to the number<br />

of rules Rn in the grammar<br />

However, since the parser - in applying a rule to the target reading found - must check<br />

("instantiate") all the rule's context conditions as true, the relevant constant is not the<br />

- 170 -

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

Saved successfully!

Ooh no, something went wrong!