Database Questionnaire Manual

Download manual as PDF

The following manual describes the guidelines that the editors asked the database contributors to follow in filling in the questionnaire. It defines all the key concepts, discusses a number of potential issues, and gives some examples.

1. Goals and motivations

The Leipzig Valency Classes Project (funded by the DFG) is carrying out a large-scale cross-linguistic comparison of valency classes (or "verb types", in terms of Levin 1993). With respect to their valency properties, verbs fall into different classes in all languages. The project is inspired by Levin (1993), a classical study of syntactic classes of verbs in English, which shows that a semantic classification of verbs can be achieved through applying syntactic diagnostics. Yet, this study, as well as an earlier study by Apresjan (1967) on Russian, has not been followed up cross-linguistically, which leaves open the question of which aspects of these classifications are universal and which are language-particular. Similarly, valency dictionaries are few in number and mostly deal with European languages, thus they cannot fill the gap.


2. Project contributions

To make progress in the cross-linguistic study of valency classes, the members of the Valency Classes Project (Andrej Malchukov, Martin Haspelmath, Bernard Comrie, Iren Hartmann) have assembled a group of contributors, specialists of valency patterns in a representative set of languages, who are collaborating to obtain a consistent set of cross-linguistic data. The contributors have been asked to do three things as part of their contribution to the project:

  1. fill in the database questionnaire, which (minimally) asks for valency information on a set of 70 verb meanings (taken as representative of the verbal lexicon) for each project language; individual databases will be published as part of an online database (edited by Iren Hartmann and Martin Haspelmath)
  2. give a presentation on language-particular patterns at the Leipzig Valency Classes Conference (2011 April 14–17)
  3. contribute a paper to an edited volume on valency classes cross-linguistically (edited by Andrej Malchukov and Bernard Comrie)

In the following, the database questionnaire is described. (Items (ii) and (iii) are described elsewhere.)


3. The verb meanings

The purpose of the Valency Database Questionnaire is to gather comparable valency data on a wide variety of languages. The data will be comparable because the verbs are elicited in response to a list of 70 pre-defined verb meanings, and because the valency information is recorded in a standard way. The 70 verb meanings are described in Table 1, in three columns: (i) the meaning label, (ii) the role frame, and (iii) a typical context. (Since the English verbs used as meaning labels sometimes have different meanings, we have added a sentence for each verb meaning that makes the intended meaning clear. These sentences are not crucial, they are just intended to help the contributors find a context for a counterpart.)

Table 1: The 70 verb meanings

meaning label role frame typical context
RAIN(it) rainsIt rained yesterday.
BE DRYS is dryThe ground is dry.
BURNS burnsThe house is burning.
SINKS sinksThe boat sank.
ROLLA rollsThe ball is rolling.
BE A HUNTERS is a hunterThis man is a hunter.
BE HUNGRYE is hungryThe baby is hungry.
BE SADE is sadThe little girl was sad.
DIES diesThe snake died.
FEEL COLDS is coldI’m cold.
FEEL PAINE feels pain in MMy arm is hurting. = I’m feeling pain in my arm.
SCREAMS screamsThe man screamed.
LAUGHS laughsThe little girl laughed.
PLAYS playsThe child is playing.
LIVES lives somewhere (L)The old people live in town.
LEAVEA left LThe boy left the village.
GOS goes somewhere (L)The woman went to the market.
SINGS singsThe boy sang (a song).
JUMPA jumpsThe girl jumped.
SIT DOWNS sits down (somewhere (L))The children sat down on the bench.
SITS sits somewhere (L)The children sat on the floor.
RUNA runsThe horse is running.
CLIMBA climbs (up L)The men climbed (up) the tree.
COUGHS coughsThe old man coughed.
BLINKS blinksI blinked (my eyes).
SHAVEA shaves (his beard/hair)The man shaved his beard/cut his hair
DRESSA dresses PThe mother dressed her daughter
WASHA washes PThe mother washed the baby.
EATA eats PThe boy ate the fruit.
HELPA helps XI helped the boys.
FOLLOWA follows XThe boys followed the girls.
MEETA meets XThe men met the boys.
HUGA hugs PThe mother hugged her little boy.
SEARCH FORA searches for XThe men searched for the women.
THINKA thinks about XThe girl thought about her grandmother yesterday.
KNOWA knows PThe girl knew the boy.
LIKEE likes MThe boy liked his new toy.
FEARE fears MThe man feared the bear.
FRIGHTENA frightens PThe bear frightened the man.
SMELLE smells MThe bear smelled the boy.
LOOK ATA looks at PThe boy looked at the girl.
SEEE sees MThe man saw the bear.
TALKA talks (to X) (about Y)The girl talked to the boy about her dog.
ASK FORA asks (X) for YThe boy asked his parents for money.
SHOUT ATA shouts at XThe woman shouted at the children.
TELLA tells (X) YThe girl told the boy a funny story.
SAYA says “...”( to X)They said “no” to me.
NAMEA name X (a) YThe parents called the baby Anna.
BUILDA builds P (out of X)The men built a house out of wood.
BREAKA breaks P (with I)The boy broke the window with a stone.
KILLA kills P (with I)The man killed his enemy with a club.
BEATA beats P (with I)The boy beat the snake with a stick.
HITA hits P (with I)The boy hit the snake with a stick.
TOUCHA touches P (with I)The boy touched the snake with a stick.
CUTA cuts P (with I)The woman cut the bread with a sharp knife.
TAKEA takes P (from X)The man took the money from his friend.
TEARA tears P (from X)The girl tore the page from the book.
PEELA peels (X off) PThe boy peeled the bark off the stick.
HIDEA hides T (from X)The boy hid the frog from his mother.
SHOWA shows T (to R)The girls showed pictures to the teacher.
GIVEA gives T to RWe gave the books to the children.
SENDA sends T (to X)The girl sent flowers to her grandmother.
CARRYA carries T (to X)The men carried the boxes to the market.
THROWA throws T somewhere (L)The boy threw the ball into the window.
TIEA ties P (to L) (with I)The man tied the horse with a rope to the tree.
PUTA puts T somewhere (L)I put the cup onto the table.
POURA pours T somewhere (L)The man poured water into the glass.
COVERA covers P (with X)The woman covered the boy with a blanket.
FILLA fills P (with X)The girl filled the glass with water.
LOADA loads T (onto L)The farmer loaded hay onto the truck. = The farmer loaded the truck with hay.

This sample of 70 verbs1, which was in part selected on the basis of the feedback from the contributors2, is hoped to be representative of the verbal lexicon. It is in particular these verb meanings that have been reported to show distinctive grammatical behaviour in the literature. Of course the editors had to try to strike a balance between a temptation to include more interesting verb meanings in the list, and avoiding overload on the part of contributors if confronted with a more extensive list. Further interesting verbs could be added to the database of individual languages (see §9.2).


4. Tasks for the database contributors

Contributors are asked to provide four types of information, in four different tables of the database:

  1. counterpart verbs, in the Verbs table (§5)
  2. examples, in the Examples table (§6)
  3. coding frames, in the Coding frames table (of these verbs) (§7)
  4. valency alternations (undergone by these verbs), in the Alternations table (§8)

5. Counterpart verbs

Please find a counterpart verb in your language for each of the pre-defined verb meanings. Note that the meaning definition is given by the role frame (plus optional comments in the meaning comments field, and example), not by the meaning label (COVER, FILL, etc.). The latter is only a label that serves as a heading for the record. The meaning thus includes information about semantic roles, for which the role frame is crucial (e.g. the meaning intended by WASH is 'A washes P', not 'A washes').

For each verb meaning of the database, please find the semantically most fitting non-derived verb in the project language. More generally, the verb should have a "basic" flavour, i.e. verbs that are used very rarely should be avoided if a more commonly verb with similar meaning is available. “Basic”ness of the counterpart verbs is more important than exact semantic equivalence between the pre-defined meanings and the counterparts. The only requirement is that the correspondence is close enough to be helpful for the project.

The relationship between pre-defined meanings and counterpart verbs is many to many. This means that if there are two basic verbs in your language that correspond to a meaning, you should include them both, and if a single verb corresponds to two different meanings, it needs to be given only once.

If there is no counterpart in your language and a paraphrase would have to be used (e.g. if HIDE is expressed as 'put something somewhere where others cannot see it'), please do not give a counterpart. (This means checking the field "No counterpart" in the Meanings layout.)

This does not mean that verbs that are complex in some way should be excluded. If a complex verbal expression, whether a morphologically derived form or a syntactic phrase, is conventional (or lexicalized), it should be included, even if it is productively derived.3 Thus, complex precicates like English carry out or German teil-nehmen 'take part', as well as serial-verb complexes like Yoruba bá ... wí 'rebuke', should be regarded as single verbs.

If a verb has other meanings than the pre-defined meaning for which it is a counterpart, it is helpful to include these other meanings, in the comments field.4 (It is also possible to create new meanings; see §9.3 below for this advanced feature.)

Homonymous verbs should be distinguished by a number, e.g. lie (1) ('be in a horizontal position') and lie (2) ('say something that is untrue').

The "comments" field can contain further non-structured information about all aspects of the verb and its relationship to the pre-defined meaning.

DATABASE FIELDS:

Verb form:
Please give the verb in its usual citation form.
Comments:
You may comment on any aspect of this verb.

relationships:

Meanings:
A verb may be related to one or more meanings from the Meanings table.
Coding frames:
A coding frame needs to be entered (selected or newly created) for each verb.
Alternation values:
The alternation values (occurs regularly, occurs marginally, occurs never, no data) are best entered on the Verbs layout.
Examples:
An example (with the basic coding frame) needs to be entered (generally newly created) for each counterpart verb.
Alternation examples:
At least one example needs to be entered (generally newly created) for each alternation. This can be done on the Verbs layout, or on the Alternation values layout.

6. Examples

Please provide glossed examples of sentences illustrating the coding frames and alternations. There should be (at least) one example for each of the counterpart verbs with the basic coding frame, as well as (at least) one example of each of the alternations (with some verb).5

Ideally there would also be an example of each possible verb-alternation pair (where the verb should be shown in the non-basic alternant form). However, since some alternations are very productive and occur with a large number of verbs, this would be too much work for most contributors, so a complete set of verb-alternation pair examples is not required.

DATABES FIELDS:

Primary text:
Please give the example text in the way the language is normally written by linguists.
Original orthography:
Give the original orthography, if it differs from the way linguists write the language (e.g. if it is in a different script).
Analyzed text:
This field is for text with hyphenation or other annotation, if required for morpheme-by-morpheme glosses.
Gloss:
Morpheme-by-morpheme gloss, following the Leipzig Glossing Rules.
Translation:
Idiomatic translation into English.
Other translation:
Idiomatic translation into a major language other than English.
Comments:
Any kind of comments on the example.
Example type:
Select one example type from the list (elicited from speaker, naturalistic spoken, naturalistic written, constructed by linguist, constructed by native speaker linguist, other).

relationships:

Source person:
Give the name of the source person if the example was elicited or constructed.
Reference:
Include a reference if the example is naturalistic (written or spoken)
Pages:
Page number of reference

7. Coding frames

7.1. Defining valency

In our terminology, the valency of a verb is the list of its arguments with their coding properties (coding frame), their behavioural properties (syntactic-function frame), and with the relationship of the arguments to the roles in the verb's role frame.

Coding properties involve the following techniques (Haspelmath 2005; Malchukov, Haspelmath & Comrie 2010):

  • flagging (case or adposition marking)
  • indexing (agreement, cross-referencing)
  • word order (in the absence of other kinds of marking)

Behavioural properties concern the behaviour with respect to patterns like reflexivization, passivization, causativization, argument omission, and various cross-clausal constructions such as control, switch-reference, raising and coordination. As a verb's valency consists of both the coding properties and the behavioural properties of its arguments, all these are in principle relevant to valency. However, in the Leipzig Valency Classes Project, only coding properties and one aspect of the behavioural properties, alternations, are taken into account.

An example of a full specification of a verb's valency is given below for English remind:

English remind

coding frame: A > V.subj[A] > R > of+T
syntactic-function frame: subjectX direct.objectY oblique.objectZ
role frame: A reminds R of T (or: agentA addresseeR themeT
or: A cause (remember R T))
  • The coding frame contains information about flagging (e.g. the preposition of), indexing (e.g. the fact that the verb agrees with the subject), and word order.
  • The syntactic-function frame contains information about behavioural properties, summed up in syntactic-function labels (thus, "subject" means that the argument controls verb-indexing, can undergo raising, becomes the oblique agent in passivization, etc.). Although it is part of valency, the syntactic-function frame as such plays no role in this project, and we limit ourselves to considering the behaviour of verbs in alternations.
  • The role frame tells us how the syntactic arguments map onto semantic roles (this can be done in various ways, by simple English glosses with participant variables, by informative semantic-role labels, or by semantic decomposition with participant variables).

An argument of a verb is a phrase whose occurrence is made possible by a specific verb, and which therefore cannot occur with a generic verb. This can be tested by attempting to move a phrase into a neighboring clause with an anaphoric verb, as shown in (1a, 1c). Adjuncts, by contrast, are not tied to particular verbs and can therefore be moved out into a clause with an anaphoric verb (1b, 1d):

(1)

  1. I wrote a letter. > *I wrote, and I did a letter.
  2. I wrote with a pen. > I wrote, and I did it with a pen.
  3. I put the book on the table.
    *I put the book, and this happened on the table.
  4. I wrote the letter on the table. >
    I wrote the letter, and this happened on the table.

If you are unsure whether a participant is an argument or an adjunct, please make an arbitrary choice and include a comment in the verb layout's comment field. (Please do not use language-specific criteria for "argumenthood", because these are really criteria for different concepts labeled "argument", not for comparable 'argument' concepts.)


7.2. Representing

Different verbs have different coding frames, but in all languages, coding frames recur, e.g. in German, the sample coding frames shown in (2a-c) occur in many different verbs:

(2)

  1. A-nom X-dat:
    (helfen 'A helps X', folgen 'A follows X', dienen 'A serves X', ...)
  2. S-nom an+X:
    (denken 'S thinks of X', liegen 'S is due to X', etc.)
  3. A-nom R-acc an+T:
    (erinnern 'A reminds R of T', etc.)

(Note: capital letters other than V are used as argument/participant variables.6)

Since coding frames are not unique, but recur, they are in a separate table of the database. Once a coding frame has been set up for a verb, all other verbs using the same coding frame can make use of the same record, i.e. coding frames need to be entered only once and can thereafter be simply selected from the list of existing coding frames.

A coding frame is a list of all the argument variables with their standard coding, i.e. flagging (case-marking or adposition marking), indexing ("agreement" or "cross-referencing"), possibly word order, plus a verb variable.

The following conventions are used:

  • cases: case labels are attached to an argument variable by a hyphen, e.g. A-nom (for nominative case), R-dat, P-abs
  • adpositions: forms of adpositions are attached to an argument variable by a plus sign, e.g. for+X, à+R
  • indices: index labels are attached to the verb variable by a period, e.g. V.subj[A] (for German subject agreement), subj[A].obj[P].V (for Bantu subject and object agreement); the role information is given in brackets noun incorporation: is marked by angle brackets, e.g. A P <I>V
  • word order: if the order of elements is fairly fixed and potentially distinctive,7 an greater-than character (>) is used between elements that occur adjacent and normally in the given order (e.g. English A > V.subj[A] > P)
  • optionality: If a coding element occurs optionally or variably (i.e. only under some circumstances), it can be put in parentheses8

Note that case labels and index labels are language-specific entities, just like adpositions. There is no need to standardize (or abbreviate) them, because they will eventually have to be defined in full detail anyway (but not within our database). Transparent labels are good for mnemonic reasons, though. If word order is not consistent or particularly distinctive, the order in which the argument variables and the verb variable occur in the coding frame is in principle arbitrary, but for mnemonic reasons, an order that corresponds to the most frequent clause order is advisable.

It is important to note that the coding frame descriptions are necessarily schematic and partial and cannot possibly describe the coding fully. For example, if an index can either be a prefix or a suffix, then a salient or dominant position should be chosen, without worrying about the incompleteness of the coding frame. Another example is word order, which often obeys complex regularities that cannot possibly be captured by simple schemas.

In most cases, arguments are noun phrases or adpositional phrases with specific coding. However, arguments may also be adverbial arguments, in particular locational arguments. These arguments do not have any specific coding, cf. (3). In such cases, all we can say is that the argument is a locational phrase of some sort, and the coding frame is "A V T LOC".

(3)

  1. Put the book on the shelf
  2. Put the money under the mattress
  3. Put it here

Whether the arguments are obligatory or optional is not recorded in the coding frames, because it may depend on too many different factors, most of which have nothing to do with the verb-specific coding. If an argument can be omitted only with certain verbs, then this should be regarded as an argument-omission alternation (e.g. object omission with existenitial/generic meaning that is possible for objects of certain verbs in English: He often reads/eats/drinks).

If a verb is associated with several different coding frames that are not related by a regular alternation, then the verb has to be split up (somewhat artificially) into two different homonymous verbs. (In reality, the relationship between verbs and coding frames is many-to-many, but we simplify our database structure by pretending that it is many-to-one.)

The contributors indicate the semantic roles of the arguments by using the same variables as argument variables that are used as participant variables in the role frames of the pre-defined meanings, for instance:

pre-defined meaning label:ASK FOR
pre-defined role frame:'A asks R for T'
German counterpart verb:bitten
coding frame:A-nom V R-acc um+T

In this way, it becomes clear that the nominative argument has the asker role, the accusative argument has the askee role, and the complement of the preposition um has the role of thing asked for.

It is important to be aware that the semantic roles in the role frames do not necessarily correspond to syntactic arguments in your language. (The role frames are not "semantic valency frames", and we do not work with a semantic definition of arguments.) The role frames are intended to convey the verb's meaning and to provide readily identifiable participant variables, not to prejudge the number of syntactic arguments that a counterpart verb will have.

Note that in the role frames, some arguments are given in parentheses. This has no particular meaning, but is intended to draw attention to the fact that we do not expect all roles to correspond to arguments of the counterpart verb of your language. The roles in parentheses seem to us particularly likely not to correspond to arguments, but this is just an expectation based on our impressions. What counts are the facts of your language.

If your verb is associated with two coding frames that are related via an uncoded alternation (e.g. English give, which can have the coding frame "A > V > R > T" or the coding frame "A > V > T > to+R"), the decision of which coding frame to take as basic may not be possible on a principled basis, so an arbitrary decision may have to be taken.9

If your verb has an argument with a semantic role that is not included in the role frame, please use additional role variables and characterize the additional roles in the comment field of the coding verb.

DATABASE FIELDS:

Coding frame schema:
Please give the coding frame in schematic form as explained above
Description:
Here you should give more details of the coding frame.
Comments:
This field is for any further comments.
Coding-frame class:
See under §9.4.

8. Valency alternations

8.1. Defining alternations

For the purposes of our project, a valency alternation is defined as a set of two different coding frames that are productively (or at least regularly) associated with both members of a set of verb pairs sharing the same verb stem. (Thus, we are restricting ourselves to coding alternations.) Valency alternations may or may not be coded in the verb form, and accordingly we distinguish two types of alternations, uncoded alternations (such as the English Dative Shift alternation) and coded alternations (such as the English Passive alternation).

Examples of alternations are the following:

English:Dative Shift (uncoded)
A > V > R > T<> A > V > T > to+R
(e.g. give, sell, lend, ...)
Russian:Anticausative alternation (coded)
A-nom V X-acc<> X-nom V-sja
(e.g. lomat' 'break', otkryt' 'open', ...)
German:Passive Voice (coded)
A-nom X-acc V<> X-nom von+A V-t+werden
(e.g. nehmen, bringen, schicken, lachen, ...)

Alternations are relevant to the project to the extent they are sensitive to verb classification (e.g., some varieties of differential object marking apply to any transitive verb, which does not yield an interesting clustering of verb types). More generally for our purposes, most relevant are those alternations which are fairly productive (not restricted to a few lexical items), but ­– most importantly – are sensitive to lexical classes. That is, we are interested in alternations which are distinctive for the verbal lexicon (as sampled here) rather than in those which apply across the board or apply to just few items.

One of the alternants needs to be designated as "basic" for the purposes of the database. In a coded alternation, this will be the alternant with no coding on the verb. In an uncoded alternation (as well as in a doubly coded alternation), the contributor has to choose one alternant as "basic". It is understood that a principled decision will often be difficult or impossible, so an arbitrary decision can be taken.

Contributors will ideally enter all (major) valency alternations of their language into the "alternations" table of the database, but if there are more than ten such alternations, then this will be a lot of work, and they should contact the editors.

Then for each verb, they will have to decide whether the verb occurs in the alternation or not, or whether it applies only marginally.

DATABASE FIELDS:

Alternation name:
Please find a language-specific name (ideally capitalized) for your alternation. This has no theoretical significance and is only for reference.
Description:
Here you should describe what the alternation does. This might be done in terms of basic and derived coding frame schemas, but often additional conditions will have to be given in prose.
Alternation type:
Specify whether it is a coded or an uncoded alternation.

relationships:

Alternation values:
The alternation values (occurs regularly, occurs marginally, occurs never, no data) are best entered on the Verbs layout, but may alternatively be entered on the Alternations layout.
Alternation examples:
At least one example needs to be entered (generally newly created) for each alternation. This can be done on the Verbs layout, or on the Alternations layout.

8.2. Examples of uncoded alternations

In this subsection only uncoded alternations are considered; discussion of coded alternations is postponed to the next subsection. The two subsections should be seen as largely complementary, as alternations will be coded by dedicated markers in some languages (apparently especially languages with a richer morphology) and left uncoded in other languages (like English).

We begin with English, a rather atypical example of a language with a particularly rich set of uncoded alternations. Levin (1993) mentions, in particular, the following alternations. (The list below mentions only fairly productive alternations and does not include verb-coded alternations like the passive alternation; the terminology partially differs from Levin's.)

  1. the Ambitransitive Alternation (John broke the stick ~ The stick broke)
  2. the Middle Alternation (John cut the bread ~ The bread cuts easily)
  3. the Reflexive Omission Alternation (John washed himself ~ John washed)
  4. the Reciprocal Alternation (John married Mary ~ John and Mary married)
  5. the Dative Alternation (Mary gave the book to John ~ gave John the book)
  6. the Locative Alternation (John loaded the truck with hay ~ the hay onto the truck)
  7. the Conative Alternation (John cut the bread ~ cut at the bread)
  8. the Object Omission Alternation (John ate the bread ~ John ate).

8.3. Examples of coded alternations

Languages with richer morphology often use coded alternations for many argument alternations left uncoded in English. Thus in Even, a Tungusic language, the “middle alternation” is signaled by the mediopassive marker, the “inchoative-causative alternation” is signaled by the causative marker (in competition with the mediopassive), while equivalents of English verbs allowing for a “reciprocal alternation” commonly involve a lexicalized sociative marker (e.g. baka-lda [find-SOC] ‘meet’).

One can use taxonomy for the domain of verb-coded alternations, as we adopted for (uncoded) coding alternations:

  • Valency-reducing alternations, coming in several subtypes:
    1. Subject-demoting/deleting alternations
      • anticausative
      • middle
      • reflexive
      • reciprocal
    2. Object-demoting/deleting alternations
      • antipassive
    3. Subject-Object rearranging alternations
      • passive (differs from anticausative in that A may be expressed, or is implied)
  • Valency-increasing and valency-rearranging alternations, especially causatives and applicatives; the latter however may rearrange rather than increase the valency. In some languages, the same marker is used both in causative and applicative functions; also for such cases it is important to determine which verbs select for which function.

Note that some languages have several causative markers, for example, for building intransitive vs. transitive causatives. These can be used to test for transitivity of less prototypical transitive verbs.

There may be several subtypes of applicatives, depending on which object is promoted (for example, in Hoocąk (Siouan), there are 4 different applicative markers, including the benefactive applicative, the instrumental applicative and two types of locative applicatives). On the other hand, the general applicative in Salish has been claimed to have different meanings depending on the verb’s class. Applicatives may be used to render many of the alternations listed in §8.2, including the dative shift, or locative alternation (cf. (f)). Other languages may use directional markers to code some of these alternations (cf. Russian na-gruzit’ seno na telegu [PREF-load hay on cart] ‘to load the hay on the cart’ vs. za-gruzit’ telegu senom [PREF-load cart hay.INS] ‘to load the cart with hay’; German laden vs. be-laden).

Not all alternations can be easily classified as valency-increasing/rearranging or valency-reducing. For example, some (Austronesian) languages show a variety of “voice” (or “focus”) forms (“actor focus”, “goal focus”, etc), used for ‘promotion’ of different objects to the subject position; for these languages it will be relevant which Vs allow for which voice constructions. On the other hand, head-marking languages of the “hierarchical type” show a direct-inverse alternation triggered by the relative prominence of the A and P arguments. In that case it is relevant to study the use of direct-inverse alternations with different groups of two and three argument verbs (in the latter case, it is also relevant which of the object arguments takes part in the alternation; e.g., Theme or Recipient of a ditransitive verb). But also for the domain of monotransitives some languages may show further differentiation; e.g., some languages (like Tlapanec) may have different inverse forms for different subtypes of 2-argument verbs.


9. Optional advanced features

9.1. Ten additional verb meanings

For ten additional verb meanings, counterparts may optionally be given, see Table 2.

Table 2: Ten additional verb meanings

BRINGA brings T to RThe girl brought flowers to me.
PUSHA pushes P (somewhere (L))The boy pushed the girl (into the water).
DIGA digs (for X)The woman is digging for potatoes.
WIPEA wipes T (off X)The women wiped dirt off the table.
STEALA steals T (from X)The thief stole money from the old lady.
GRINDA grinds P (with I)The women ground the seeds (with mortar and pestle).
HEARE hears MThe boy heard the bear.
TEACHA teaches R TThe old lady taught the girl a song.
COOKA cooks PThe women cooked the meat.
BOILS boilsThe water is boiling.

9.2. Adding more verbs

For each alternation, and for each coding frame, optionally additional verbs may be entered which are not counterparts of the pre-defined meanings and which undergo the alternation and which occur in the coding frame. These further verbs should be linked to newly created meanings (see §9.3).

Ideally, the information provided on these additional verbs would be complete, i.e. it would include the coding frame (also if the verb is given as an additional example of an alternation) and the behaviour in alternations (also if the verb is given as an additional example of a coding frame).


9.3. Adding more verb meanings

In addition to the 70 pre-defined verb meanings, users may create further verb meanings if they want to enter verbs that have other meanings.

DATABASE FIELDS:

Meaning label:
The meaning label is the closest English verb, in capitals.
Role frame:
Please give a role frame involving variables for the arguments so that coding frames can be related to the meanings of the verbs.
Comments:
You may give any kinds of comments.

9.4. Characterizing coding-frame classes

If a coding frame is used for an open class of verbs (i.e. if it is productive), please specify (optionally) which verbs may belong to this class (in terms of relevant semantic or formal features). This should be done in the field "Coding-frame class". (For highly restricted classes, the best way of characterizing them would be to give additional verbs, see §9.2.)


References

Apresjan, Jurij D. 1967. Eksperementaljnoe issledovanie russkogo glagola. Moskva: Nauka.

Dixon R. M. W. 1991/2002. A New Approach to English Grammar, on Semantic Principles. Oxford: Clarendon Press.

Haspelmath, Martin. 2005. Ditransitive Constructions: The Verb ‘Give’. In: Haspelmath & al. (eds.), 426–429.

Levin, Beth. 1993. English Verb Classes and Alternations. Chicago: University of Chicago Press

Malchukov, Andrej, Martin Haspelmath, and Bernard Comrie. 2010. Ditransitive constructions: a typological overview. To appear in Malchukov, A., M. Haspelmath, and B. Comrie (eds.). Studies in Ditransitive constructions. A comparative handbook. Berlin: De Gruyter Mouton.

Sauerland, Uli. 1994. German diathesis and verb morphology. In: Jones, Doug (ed). 1994. Working Papers and Projects on Verb Class Alternations in Bangla, German, English, and Korean. MIT AI Memo 1517, 37–92.


Footnotes

  1. Note that the ordering of the verbs in Table 1 (from potentially/frequently zero-valent, through monovalent and divalent to trivalent) is somewhat different from the ordering in the database. The ordering is of course irrelevant.
  2. Please note that the list of verbs was somewhat updated with respect to the June 2010 version of the questionnaire and of the database (at the time there were some discrepancies between them).
  3. In some cases, it is impossible to give basic counterparts, as in the case where all ditransitives including 'give' are derived (applicative, as in the Mayan language Tzotzil). Therefore it is important to provide information about morphological complexity of Vs. This question is relevant also insofar as the morphological make-up may determine the availability of a certain valency pattern. For example, in Malayalam, only derived ditransitives (causatives of transitives), take a double object construction, while basic (underived) ditransitives take a dative construction.
  4. This question is relevant insofar as the valency pattern may be motivated through one of the meanings of the polyfunctional item. For example, in some languages, which use the same verbs for both ‘hit’ and ‘throw’, this verb follows the allative pattern, as expected for caused motion verbs. Similarly, a verb may have a valency pattern that is motivated by its etymological meaning, not by any of the current meanings.
  5. If the alternation patterns are different for different subclasses of verbs, the contributor is requested to provide several examples illustrating the differences (e.g., if the causative derivation produces different structures when applied to intransitives and transitives, as is frequently the case; here at least two examples of the causative construction should be given).
  6. We often use letters that can be thought of as standing mnemonically for particular roles (A: agent, P: patient, S: single central argument of intransitive verb, T: theme (of ditransitive verb), R: recipient (of ditransitive verb), L: location (including goal), I: instrument, E: experiencer, M: stimulus, X, Y, Z: other). No claims are associated with the use of these letters, and they could be replaced by other arbitrary variable symbols.
  7. Some languages make word-order distinctions depending on the valency class. Thus, in (Gao) Songhay, canonical transitives (‘break’, ‘kill’) have SOV order, while less canonical bivalent verbs (‘see’, ‘follow’, ‘love’) have SVO order.
  8. Two coding frames may differ only in the optionality vs. obligatoriness of a coding element. For example, in the Austronesian language Manam some experiencer verbs (‘like’, ‘know’, ‘be bad at’) use primary-object indexing only when the primary object is prominent, while canonical transitives (like ‘break’), invariably index the primary object. And in Newari, the availability of an ergative pattern depends on tense, on the one hand, and on lexical class of the verb, on the other hand, so that two-argument verbs deviating from the transitive prototype can take the ergative pattern optionally.
  9. We considered two ways of avoiding an arbitrary choice: (i) by allowing the association of a verb with two or more coding frames (but in this way, we would have lost the information that the use of two coding frames is systematic rather than verb-specific), and (ii) by capturing alternations in a very different way, not via a separate alternations table, but via different coding frames that may be associated with a single verb stem (but in this way, we would have lost the ability of comparing alternations across languages). Clearly, no choice of representation mode is ideal.