-
Notifications
You must be signed in to change notification settings - Fork 0
3. Constructicon entries: definition of the fields
Constructions are stored as entries in the Italian Constructicon. Each entry contains a number of fields, which specify formal, functional and usage information about the construction, as well as its relatedness to other entries in the Constructicon. In this page, we describe the type of information contained and the guidelines for the annotation of each field.
- ID
- Name
- CoNLL-X formalization
- Definition
- Restrictions
- Collocational preferences
- Usage
- Formal Tags
- Functional Tags
- Complexity-level Tags
- Category Tags
- Schematicity
- Links
- Examples
- Notes
- CEFR Level
- References
- Data collector
A unique and stable identifier for the constructional entry. This field is filled automatically as a new construction is created.
Contains a “human-intelligible” name for the construction.
In order to keep a consistent naming practice, we use the following decision tree to work out the name for each entry:
- Is there a standard denomination for this construction (i.e., in literature)? If so, use it. If there is not a commonly accepted denomination, go to 2.
- Can the name be expressed by means of its lexicalized components (e.g., "capo-N" for capo + Noun compounds)? If so, build the name that way. If there are no lexicalized components, go to 3.
- Can the name be expressed by means of its syntactic relations (e.g., "Sbj V Obj1 Obj2" for the Ditransitive construction)? If so, build the name that way as long as it is easily readable. If it is not, go to 4.
- Can the name be easily expressed by the function (e.g., "Contrastive Focus")? If so, name the construction with reference to its function. If the name is too generic, or if using the function as name is not possible for some other reason, go to 5.
- If none of the previous criteria yield an easily readable/recognizable name, just be creative and we’ll find a better name with time!
[Brief description of conll, there will be a specific file]
This field contains a description of the construction's function. Differently from the Function subfield in the CoNLL-X formalization, it is a non-formal, discursive description, similar to lexicographic definitions, and includes information on:
- semantics;
- pragmatic and discourse functions;
- information status and information structure features.
Differently from lexicographic definitions, it does not include examples, which are provided in a separate field. Definitions can be more or less elaborate, depending on the information available in the literature. An example of possible definition is given below (from salta fuori che V 'turns out that' entry):
A new piece of information comes to the speaker's knowledge from an external source. The information acquired is often unexpected or contradicts the speaker's expectations on the state of affairs, thus generating surprise in the speaker. However, since the moment of acquisition and the moment of enunciation are distinct, this construction does not convey that the speaker is currently surprised, but it is used to convey or generate surprise in the audience.
This field contains a discursive description of the constraints on the construction fillers. Such constraints can be both hard (i.e., categorical) and soft constraints (i.e., they could be violated in some specific cases). Possible constraints can include:
- formally or semantically defined types/categories of lemmas and/or words (e.g., motion verbs, two-sillable words);
- specific lemmas/words;
- formal or semantic features of the fillers (e.g., a noun cannot be plural in a specific construction).
However, further constraints on the contextual and/or co-textual environment are not included in this field (see Usage and Notes instead). The restrictions can include both the ones already specified in the ConLL-X formalization subfields, and further possible constraints that are not included/cannot be specified in the formalization.
This field includes (max. 3) "usage" tags for the construction. The tags are used if a construction is constrained or shows some preferences in its extra-linguistic behavior (i.e., if it is typically or only found in some contexts).
By extra-linguistic behavior here we refer to three possible axes: style, modality and (sociolinguistic) variety. For each of the three axes, only one of the following tags can be used:
- Style: Formal or Informal
- Modality: Spoken or Written
- Variety: Standard or Non-standard
Thus, this field cannot contain both, e.g., a "Spoken" and a "Written" tag. In that case, the information would not be relevant, since the use of the construction would not be marked in any case.
Further comments on the usage tags can be specified in the Notes field, as well as other types of information (e.g., constraints on text genres in which the constructions is found).
If none of the tags above is relevant, this field can be left empty.
list of Comparative Concepts from MoCCa (Model of Comparative Concepts for Aligning Constructicons)
[TODO: add possibilities] https://comparative-concepts.github.io/cc-database/
- word
- phrase
- clause
- beyond-clause
- adjective,
- adverb,
- conjunction,
- discourse marker,
- interjection,
- noun,
- preposition,
- pronoun,
- verb,
- onomatopoeia,
- not applicable,
- other
- lexically filled
- partially filled/schematic
- fully schematic
filled automatically from conll
filled automatically from conll
filled automatically from conll
da strutturare
- A1
- A2
- B1
- B2
- C1
- C2
This field contains citations to the relevant literature on the construction. Each citation is in the author-date format (e.g., Goldberg 1995) and is linked to its full reference Bibliography section of the AdoC website.
This field contains the name and surname of the data collector.