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.

3.8 Mapping: From word class to syntax<br />

Rules at the mapping level of a Constraint Grammar exploit (more or less)<br />

disambiguated morphological/PoS information for assigning a context dependent<br />

syntactic function potential to each target word in the text. Rules can address words<br />

individually, but are usually bundled for certain types of word class targets.<br />

Contextually safe mapping rules are able to map a more precise syntactic tag list<br />

(ideally, one tag only) than more broad rules. Therefore, unlike disambiguation rules,<br />

which remove information rather than add it, mapping rules are inherently sequential<br />

and mutually exclusive: Safe, specific, context rich rules have to be applied before more<br />

general, poor context rules, and once targeted, a word has to be “closed” for further<br />

mapping. Otherwise, every word will receive the full combined syntactic tag potential<br />

of all mapping rules targeting it, which would “erase” the visibility of any individual,<br />

more specific rule. In the rule compiler formalism used here, ordinary sequential<br />

mapping rules are marked by the MAP operator, and they are applied in the order given<br />

in the rules file of the grammar. Rules with the alternative ADD operator are cumulative<br />

and, in principle, non-sequential. Basically, ADD rules provide a way of splitting a<br />

complex MAP rule into smaller, more manageable parts.<br />

There is no clear border line between mapping rules and (syntactic)<br />

disambiguation rules. In theory, all mapping rules could be crafted with a perfect and<br />

complete list of context conditions such that no mapping would need to be ambiguous -<br />

with no need for ordinary disambiguation rules. However, in none of the presently<br />

available rule compilers can mapping rules “see” the output of other (earlier) mapping<br />

rules, making it difficult if not impossible to address syntactic context (@tags) other<br />

than that provided by lexicon entries. Also, a perfect (i.e. unambiguous) MAP rule is<br />

like a SELECT rule in the way it works - a risky kind of rule, stating a grammatical<br />

“fact” all in one go. REMOVE rules, operating on broadly mapped - and therefore<br />

ambiguous - @tag strings, are much more cautious and robust, working together step by<br />

step, relying on each other’s context condition safety nets.<br />

The basic skeleton of syntactic mapping is the target word class condition. Even<br />

without further context conditions, word class mapping can provide a working mapping<br />

module for a syntactic disambiguation CG to work on. The Portuguese mapping rule set<br />

is structured in word class “chapters”, with each chapter concluded by a “pure” word<br />

class mapping rule, preceded by more specific rules for that word class, and headed by a<br />

section with word or base form mapping rules. Though there are some prototypical<br />

relations, most form-function pairs (PoS-@tag pairs) are not very closely knitted. Thus,<br />

nouns are typical of subject (@SUBJ) and direct object (@ACC) function, but still,<br />

subjects do come as infinitive clauses (#ICL), too, and objects can be finite subclauses<br />

(#FS, “acho que não faz nada”). Adjectives and participles often occur with adnominal<br />

and predicative function, but they can head noun phrases, too, and thus usurp typical<br />

- 182 -

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

Saved successfully!

Ooh no, something went wrong!