| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| en:pojmy:ud [2023/04/03 16:01] – [Syntactic functions] alexandrrosen | en:pojmy:ud [2024/10/08 21:50] (current) – [About UD-annotated InterCorp] alexandrrosen |
|---|
| ====== Universal Dependencies – UD ====== | ====== Universal Dependencies – UD ====== |
| |
| [[https://universaldependencies.org|Universal Dependencies]] is a framework for consistent annotation of grammar (parts of speech, morphological features, and syntactic dependencies) across different human languages. UD is an open community effort with over 300 contributors producing nearly 200 treebanks in over 100 languages. A recent version of the [[en:cnk:intercorp|InterCorp]] parallel corpus ([[en:cnk:intercorp:verze13ud|13ud]]) has been annotated in terms of morphological categories, syntactic functions and syntactic structure following the UD guidelines and using the tools developed within the UD project. | [[https://universaldependencies.org|Universal Dependencies]] is a an open international project aiming at linguistic annotation consistent across different languages. Some recent versions of the [[en:cnk:intercorp|InterCorp]] parallel corpus ([[en:cnk:intercorp:verze13ud|13ud]] and [[en:cnk:intercorp:verze16ud|16ud]]) have been annotated in terms of morphological categories, syntactic functions and syntactic structure following the UD guidelines and using the tools developed within the UD project. |
| |
| General guidelines for annotation are provided on the UD project website ([[https://universaldependencies.org/guidelines.html|UD Guidelines]]), including a detailed description of: | General guidelines for annotation are provided on the UD project website ([[https://universaldependencies.org/guidelines.html|UD Guidelines]]), including a detailed description of: |
| |
| Key specifics of the UD annotation as used in InterCorp: | Key specifics of the UD annotation as used in InterCorp: |
| * In other releases of InterCorp, word class and morphological categories of a word are specified as the value of the ''tag'' attribute. For most languages, InterCorp release 13ud retains these language-specific tags in the ''xpos'' attribute. However, the UD **word class** and **morphological categories**, denoted uniformly for all languages, are listed separately as values of the ''upos'' and ''feats'' attributes (see below [[en:pojmy:ud#parts_of_speech|Parts of speech]], and [[en:pojmy:ud#other_categories|Other categories]], respectively). Frequently used morphological categories from the ''feats'' list have been promoted to the status of regular attributes at the same level as ''upos''. This applies, for example, to morphological case, number, gender or person (''case'', ''number'', ''gender'', ''person''). | * In other releases of InterCorp, word class and morphological categories of a word are specified as the value of the ''tag'' attribute. In the UD annotation, these language-specific tags are retained for most languages, in the ''xpos'' attribute. However, the UD **word class** and **morphological categories**, denoted uniformly for all languages, are listed separately as values of the ''upos'' and ''feats'' attributes (see below [[en:pojmy:ud#parts_of_speech|Parts of speech]], and [[en:pojmy:ud#other_categories|Other categories]], respectively). Frequently used morphological categories from the ''feats'' list have been promoted to the status of regular attributes at the same level as ''upos''. This applies, for example, to morphological case, number, gender or person (''case'', ''number'', ''gender'', ''person''). |
| * For use in KonText, **fused forms** or //aggregates//, ie word forms composed of two or even three syntactic words, were modified as divided tokens. In English it concerns, for example, the forms //isn't// or //cannot//. For more details see [[en:pojmy:ud#multi-part_tokens|Multi-part tokens]] below. | * For use in KonText, **fused forms** or //aggregates//, ie word forms composed of two or even three syntactic words, were modified as divided tokens. In English it concerns, for example, the forms //isn't// or //cannot//. For more details see [[en:pojmy:ud#multi-part_tokens|Multi-part tokens]] below. |
| * Each word is assigned its **syntactic function** (''deprel'' – see [[en:pojmy:ud#syntactic_functions|Syntactic functions]]) and its syntactic governor in the dependency tree (''head''). To facilitate orientation in the syntactic structure, each word is also annotated with references to important properties of its head (lemma, part of speech and morphological categories), see [[en:pojmy:ud#references_to_syntactic_heads|References to syntactic head]]. If a content word occurs with a **function word** (eg. preposition, auxiliary verb, subordinate conjunction, determiner), the content word includes some properties of the function word (see [[en:pojmy:ud#references_to_function_words|References to function words]]). | * Each word is assigned its **syntactic function** (''deprel'' – see [[en:pojmy:ud#syntactic_functions|Syntactic functions]]) and its syntactic governor in the dependency tree (''head''). To facilitate orientation in the syntactic structure, each word is also annotated with references to important properties of its head (lemma, part of speech and morphological categories), see [[en:pojmy:ud#references_to_syntactic_heads|References to syntactic head]]. If a content word occurs with a **function word** (eg. preposition, auxiliary verb, subordinate conjunction, determiner), the content word includes some properties of the function word (see [[en:pojmy:ud#references_to_function_words|References to function words]]). |
| * **Annotations between languages differ** in the number of categorial attributes and in links to function words, see {{cnk:intercorp:ud_ic_attributes.pdf | List of attributes by language}}, described below in [[en:pojmy:ud#description_of_the_list_of_attributes|Description of the list of attributes]]. | * **Annotations between languages differ** in the number of categorial attributes and in links to function words, see [[en:pojmy:ud#description_of_the_list_of_attributes|Description of the list of attributes]] below. |
| * KonText supports queries by word class and other morphological categories using the **''Insert tag''** function, which inserts a UD POS (''upos'') and any category from the ''feats'' list into the query. The ''Insert tag'' feature is available for all linguistically annotated languages. | * KonText supports queries by word class and other morphological categories using the **''Insert tag''** function, which inserts a UD POS (''upos'') and any category from the ''feats'' list into the query. The ''Insert tag'' feature is available for all linguistically annotated languages. |
| ===== Morphological annotation ===== | ===== Morphological annotation ===== |
| * A list of such pairs is the value of the ''feats'' attribute. | * A list of such pairs is the value of the ''feats'' attribute. |
| * Categories in the ''feats'' attribute are separated by "|", e.g. the Russian form //школы// /'ʂkolɨ/ 'school' in genitive singular is marked as ''feats=%%"Animacy=Inan|Case=Gen|Gender=Fem|Number=Sing"%%''. | * Categories in the ''feats'' attribute are separated by "|", e.g. the Russian form //школы// /'ʂkolɨ/ 'school' in genitive singular is marked as ''feats=%%"Animacy=Inan|Case=Gen|Gender=Fem|Number=Sing"%%''. |
| * In an advanced query using the CQL query language each category can be specified separately: the Czech form //moře// 'sea' is one of the answers to the query ''%%[upos="NOUN" & feats="Number=Sing"]%%''. The Russian form is found follwoing the query ''[upos=%%"NOUN"%% & feats=%%"Gender=Fem"%% & feats=%%"Case=Gen"%%]''. The order of categories in the query is irrelevant. | * In an advanced query using the CQL query language each category can be specified separately: the Czech form //moře// 'sea' is one of the answers to the query ''%%[upos="NOUN" & feats="Number=Sing"]%%''. The Russian form is found following the query ''[upos=%%"NOUN"%% & feats=%%"Gender=Fem"%% & feats=%%"Case=Gen"%%]''. The order of categories in the query is irrelevant. |
| * The value of ''feats'' can also be treated as a string of characters using regular expressions, e.g. ''[upos=%%"NOUN"%% & feats=%%".*Case=Gen.*Gender=Fem.*"%%]''. Here the order of categories in the query should correspond to their order in the corpus. The result is the same in both cases. | * The value of ''feats'' can also be treated as a string of characters using regular expressions, e.g. ''[upos=%%"NOUN"%% & feats=%%".*Case=Gen.*Gender=Fem.*"%%]''. Here the order of categories in the query should correspond to their order in the corpus. The result is the same in both cases. |
| * Some of the categories in ''feats'' are listed also outside the list as **categorial attributes** at the same level as ''upos''. As a result, a query for a singular noun can be simply as follows: ''%%[upos="NOUN" & number="Sing"]%%''. Similarly, the query for the Russian form ''[upos=%%"NOUN"%% & %%gender="Fem"%% & %%case="Gen"%%]'' gives the same result as the two queries above. Categorial attributes can be also used to generate frequency lists.((Note that for technical reasons the names of the categorial attributes are all in lower case, including names such as ''VerbForm'' (in ''feats''), rendered as ''verb_form'', or ''NumType'', rendered as ''num_type''. The attribute values, such as ''Fem'', retain the initial upper case character, but are enclosed in double quotes, like other non-embedded attributes.)) Such attributes appear on the <fc #f4a460>light brown</fc> background in {{cnk:intercorp:ud_ic_atributy.pdf|Attribute list by language}} or in KonText in the lower part of the table shown in ''View'' / ''Corpus-specific settings...'' . | * Some of the categories in ''feats'' are listed also outside the list as **categorial attributes** at the same level as ''upos''. As a result, a query for a singular noun can be simply as follows: ''%%[upos="NOUN" & number="Sing"]%%''. Similarly, the query for the Russian form ''[upos=%%"NOUN"%% & %%gender="Fem"%% & %%case="Gen"%%]'' gives the same result as the two queries above. Categorial attributes can be also used to generate frequency lists.((Note that for technical reasons the names of the categorial attributes are all in lower case, including names such as ''VerbForm'' (in ''feats''), rendered as ''verb_form'', or ''NumType'', rendered as ''num_type''. The attribute values, such as ''Fem'', retain the initial upper case character, but are enclosed in double quotes, like other attribute values outside ''feats''.)) Such attributes appear on the <fc #f4a460>light brown</fc> background in {{cnk:intercorp:ud_ic_attributes.pdf|Attribute list by language}} or in KonText in the lower part of the table shown in ''View'' / ''Corpus-specific settings...'' . |
| |
| ^ category ^ gloss ^ example values ^ | ^ category ^ gloss ^ example values ^ |
| * Some tokens, in the UD parlance called **fused words**, or **aggregates** in some Czech corpus-related literature, consist of multiple parts. These parts correspond to different nodes in the syntactic structure. In English, such tokens represent **contractions**, consisting of a verb and the negative particle such as //isn't// or //cannot//. | * Some tokens, in the UD parlance called **fused words**, or **aggregates** in some Czech corpus-related literature, consist of multiple parts. These parts correspond to different nodes in the syntactic structure. In English, such tokens represent **contractions**, consisting of a verb and the negative particle such as //isn't// or //cannot//. |
| * The orthographic form of these words is preserved in the corpus, the individual parts are separated only in the annotation - e.g. in the value of the ''lemma'' attribute, with the "|" sign as the separator. It is therefore possible to search for them like other words, by typing the full form into the search box in a simple query (e.g. //ses// in Czech, //can't// in English or //byłbym// in Polish), or in the advanced query using the CQL search language give the same strings as the value of the **''word''** attribute . | * The orthographic form of these words is preserved in the corpus, the individual parts are separated only in the annotation - e.g. in the value of the ''lemma'' attribute, with the "|" sign as the separator. It is therefore possible to search for them like other words, by typing the full form into the search box in a simple query (e.g. //ses// in Czech, //can't// in English or //byłbym// in Polish), or in the advanced query using the CQL search language give the same strings as the value of the **''word''** attribute . |
| * In some languages, including English and Czech, a part of the fused token has a different form when occuring in a different context as an orthographically separate word. E.g. //n't//, a part of //isn't//, corresponds to //not//, the Czech auxiliary clitic //s//, a part of //ses//, corresponds to //jsi//. Both variants are represented in the annotation: the **''iword''** attribute shows the original form ''is|n't'' or ''se|s'', while the **''sword''** attribute shows the unabreviated, "reconstructed" version: ''is|not'' or ''se|jsi''.((Aggregates are present in the following languages: ar, ca, cs, de, el, en, es, fi, fr, he, it, pl, pt, tr and uk. A list of all aggregates for a given language is displayed as the frequency distribution of word forms following the query %%[sword = ".|.+"]%%.)) | * In some languages, including English and Czech, a part of the fused token has a different form when occurring in a different context as an orthographically separate word. E.g. //n't//, a part of //isn't//, corresponds to //not//, the Czech auxiliary clitic //s//, a part of //ses//, corresponds to //jsi//. Both variants are represented in the annotation: the **''iword''** attribute shows the original form ''is|n't'' or ''se|s'', while the **''sword''** attribute shows the unabbreviated, "reconstructed" version: ''is|not'' or ''se|jsi''.((Aggregates are present in the following languages: ar, ca, cs, de, el, en, es, fi, fr, he, it, pl, pt, tr and uk. A list of all aggregates for a given language is displayed as the frequency distribution of word forms following the query %%[sword = ".|.+"]%%.)) |
| * In addition to the English tokens //isn't// (''is|n't'' – ''is|not'') or //cannot// (''can|not''),((The first form, preceding the dash, is the original form, i.e. the value of the ''iword'' attribute, the second form, after the dash, is the reconstructed form, i.e. the value of the ''sword'' attribute. If a parenthesis includes just one form, the two options are identical, or the given language does not provide reconstructed forms.)) in Czech there are tokens such as //abychom// (''a|bychom'' – ''aby|bychom''), //bylas// (''byla|s'' – ''byla|jsi'') or //oč// (''o|č'' – ''o|co''); in German //zur// (''zu|r'' – ''zu|der'') or //am// (''a|m'' – ''an|dem''); in Polish //miałam// (''miała|m''), //żebyś// (''że|by|ś'') or //chciałbym// (''chciał|by|m''); in French //des// (''de|s'' – ''de|les''), //aux// (''au|x'' – ''à|les'') or //auquel// (''au|quel'' – ''à|lequel''). | * In addition to the English tokens //isn't// (''is|n't'' – ''is|not'') or //cannot// (''can|not''),((The first form, preceding the dash, is the original form, i.e. the value of the ''iword'' attribute, the second form, after the dash, is the reconstructed form, i.e. the value of the ''sword'' attribute. If a parenthesis includes just one form, the two options are identical, or the given language does not provide reconstructed forms.)) in Czech there are tokens such as //abychom// (''a|bychom'' – ''aby|bychom''), //bylas// (''byla|s'' – ''byla|jsi'') or //oč// (''o|č'' – ''o|co''); in German //zur// (''zu|r'' – ''zu|der'') or //am// (''a|m'' – ''an|dem''); in Polish //miałam// (''miała|m''), //żebyś// (''że|by|ś'') or //chciałbym// (''chciał|by|m''); in French //des// (''de|s'' – ''de|les''), //aux// (''au|x'' – ''à|les'') or //auquel// (''au|quel'' – ''à|lequel''). |
| |
| * In some languages, some deprels may have **subtypes**. The subtype name follows the colon after the deprel name, e.g. ''acl:relcl'' indicates an attribute expressed by a relative clause. The list below contains only subtypes relevant to English and represented in the corpus. Functions with subtypes for all languages are listed at [[https://universaldependencies.org/u/dep/index.html|Universal Dependency Relations]]. | * In some languages, some deprels may have **subtypes**. The subtype name follows the colon after the deprel name, e.g. ''acl:relcl'' indicates an attribute expressed by a relative clause. The list below contains only subtypes relevant to English and represented in the corpus. Functions with subtypes for all languages are listed at [[https://universaldependencies.org/u/dep/index.html|Universal Dependency Relations]]. |
| * When querying a deprel that may have a subtype, a possible subtype should be taken into account. For example, to find all words with the deprel ''acl'', whether or not the deprel has a subtype, use the expression ''%%deprel="acl.*"%%'' instead of ''%%deprel="acl"%%''. To find all auxiliary verbs, use the expression ''%%deprel="aux.*"%%'' instead of ''%%deprel="aux"%%''. To find all subjects, use the expression ''%%deprel="nsubj.*"%%''. | * When querying a deprel that may have a subtype, a possible subtype should be taken into account. For example, to find all words with the deprel ''acl'', whether or not the deprel has a subtype, use the expression ''%%deprel="acl.*"%%'' instead of ''%%deprel="acl"%%''. To find all auxiliary verbs, use the expression ''%%deprel="aux.*"%%'' instead of ''%%deprel="aux"%%''. To find all subjects, use the expression ''%%deprel="nsubj.*"%%''. |
| * When a queried deprel targets a **coordinated structure**, only the first conjunct is found. The second and subsequent conjuncts are marked as ''%%deprel="conj"%%''. The syntactic function of the entire coordination is thus specified by the ''deprel'' attribute of the first cunjunct, the head of all other conjuncts. To query the "true" deprel of a non-initial conjunct (''%%deprel="conj"%%''), use the ''p_deprel'' attribute. See [[en:pojmy:ud#coordination|Coordination]] below for details. | * When a queried deprel targets a **coordinated structure**, only the first conjunct is found. The second and subsequent conjuncts are marked as ''%%deprel="conj"%%''. The syntactic function of the entire coordination is thus specified by the ''deprel'' attribute of the first conjunct, the head of all other conjuncts. To query the "true" deprel of a non-initial conjunct (''%%deprel="conj"%%''), use the ''p_deprel'' attribute. See [[en:pojmy:ud#coordination|Coordination]] below for details. |
| |
| |
| |
| * In addition to the pointer to its head (''head'' as the word ID of the head, i.e. its word order position within the sentence, or ''parent'' as its position relative to the given word), some other attributes of the head are listed for each token: lemma (''p_lemma''), POS (''p_upos''), morphological category (''p_feats''), and syntactic function (''p_deprel''). | * In addition to the pointer to its head (''head'' as the word ID of the head, i.e. its word order position within the sentence, or ''parent'' as its position relative to the given word), some other attributes of the head are listed for each token: lemma (''p_lemma''), POS (''p_upos''), morphological category (''p_feats''), and syntactic function (''p_deprel''). |
| * A token may also have attributes that specify the properties of a fuction word that depends on the token. For example, the lemma of a preposition is shown by the attribute ''case_lemma'', morphological categories of an auxiliary by ''aux_feats'', morphological categories of a copula by ''cop_feats'', part of speech of a determiner by ''det_upos'', lemma of a marker by ''mark_lemma''. | * A token may also have attributes that specify the properties of a function word that depends on the token. For example, the lemma of a preposition is shown by the attribute ''case_lemma'', morphological categories of an auxiliary by ''aux_feats'', morphological categories of a copula by ''cop_feats'', part of speech of a determiner by ''det_upos'', lemma of a marker by ''mark_lemma''. |
| * Similar means of representing syntactic structure are used by other syntactically annotated corpora available in the KonText browser (e.g. ''syn2020''). | * Similar means of representing syntactic structure are used by other syntactically annotated corpora available in the KonText browser (e.g. ''syn2020''). |
| |
| * The second and subsequent conjuncts always depend on the first conjunct. Their syntactic function is specified as ''conj''. | * The second and subsequent conjuncts always depend on the first conjunct. Their syntactic function is specified as ''conj''. |
| * Conjunctions depend on the following conjunct. Their syntactic function is ''cc''. | * Conjunctions depend on the following conjunct. Their syntactic function is ''cc''. |
| * A reference to the so-called effective head is used to identify the head regardless of whether the token is a conjunct or not, or whether it is in the initial or non-initial conjunct: the ''e_id'' attribute refers to its identifier (the sequence number of the token representing the head within the sentence), the ''eparent'' attribute to its position relative to the token. | * A reference to the so-called effective head is used to identify the head regardless of whether the token is a conjunct or not, or whether it is in the initial or non-initial conjunct: the ''e_id'' attribute refers to its identifier (the sequence number of the token representing the head within the sentence), the ''eparent'' attribute to its position relative to the token. |
| * To find all words with a certain syntactic function, including those that are part of a coordination, use the ''p_deprel'' attribute. This attribute shows the syntactic function of the token's head. For example, a query for all indirect objects, including coordinated ones, can be formulated using the disjunction operator (%%|%%) as follows: ''%%[deprel="obj" | deprel="conj" & p_deprel="obj"]%%''. | * In InterCorp [[en:cnk:intercorp:verze16ud|release 16ud]], there is an additional ''e_deprel'' attribute whose value equals ''deprel'' of the given token, except when the token is a non-initial conjunct, i.e. when its ''deprel'' equals ''conj''. Then the value of ''e_deprel'' equals the value of ''p_deprel'', i.e. shows the syntactic function of the whole coordination. |
| | * The ''e_deprel'' attribute has the same value as ''p_deprel'' also when the ''deprel'' attribute equals ''fixed'', ''flat'', ''compound'' or ''list''. Tokens within such constructions can also be found using the syntactic function of the whole construction, i.e. the ''e_deprel'' attribute. |
| | * To find all words with a certain syntactic function, including those that are part of a coordination, in InterCorp [[en:cnk:intercorp:verze13ud|release 13ud]], where the ''e_deprel'' attribute is not available, the solution is to use the ''p_deprel'' attribute. This attribute shows the syntactic function of the token's head. For example, a query for all direct objects, including coordinated ones, can be formulated using the disjunction operator (%%|%%) as follows: ''%%[deprel="obj" | deprel="conj" & p_deprel="obj"]%%''. |
| ===== UD and KonText ===== | ===== UD and KonText ===== |
| |
| === Basic query === | === Basic query === |
| |
| * A basic query for a word form or phrase is entered in the same way as in previous releases of InterCorp.((In a basic query, it is no longer necessary in some languages to separate parts of the aggregate with a space, eg //był//, //by//, and //m// of the Polish agglutinated form //byłbym // or //is// and //n't// of the English contraction //isn't//, even in a longer expression (//aren't I//). However, a basic query for //is// or //n't// will not show concordances including the for //isn't//.)) | * A basic query for a word form or phrase is entered in the same way as in previous releases of InterCorp.((In a basic query, it is no longer necessary in some languages to separate parts of the aggregate with a space, eg //był//, //by//, and //m// of the Polish agglutinated form //byłbym // or //is// and //n't// of the English contraction //isn't//, even in a longer expression (//aren't I//). However, a basic query for //is// or //n't// will not show concordances including the form //isn't//.)) |
| |
| === Query for a lemma and a morphological tag === | === Query for a lemma and a morphological tag === |
| * [[https://www.korpus.cz/kontext/view?q=~MwKKiaMYIgcg|This query]] finds indirect objects. | * [[https://www.korpus.cz/kontext/view?q=~MwKKiaMYIgcg|This query]] finds indirect objects. |
| * The lemma of the indirect object's head can be listed using frequency distribution according to the attribute ''p_lemma''. | * The lemma of the indirect object's head can be listed using frequency distribution according to the attribute ''p_lemma''. |
| | * Note that in UD, dative complements in languages such as German or Czech are non-core dependents. As such, they should be labelled as ''%%deprel="obl"%%'' or (preferably but not obligatorily) ''%%deprel="obl:arg"%%''. For more details see [[https://universaldependencies.org/u/overview/syntax.html#core-arguments-vs-oblique-modifiers|Core Arguments vs. Oblique Modifiers]]. |
| |
| |
| === Direct or indirect objects, also as conjuncts === | === Direct or indirect objects, also as conjuncts === |
| |
| <code>[deprel="i?obj" | deprel="conj" & p_deprel="i?obj"]</code> | <code>[e_deprel="i?obj"]</code> |
| |
| * [[https://www.korpus.cz/kontext/view?q=~TwkkE2u668ya|This query]] finds direct or indirect objects, even as non-initial conjuncts, e.g. in the sentence //In Trump, they have found a shameless **frontman** and TV **personality** who will do their bidding.// | * [[https://www.korpus.cz/kontext/view?q=~ROysAM6KwymO|This query]] finds direct or indirect objects, even as non-initial conjuncts, e.g. in the sentence //In Trump, they have found a shameless **frontman** and TV **personality** who will do their bidding.// |
| * Note that for coordinated constituents, a separate concordance is shown for each conjunct. | * Note that for coordinated constituents, a separate concordance is shown for each conjunct. |
| * Either the keyword's ''deprel'' denotes the direct or indirect object (''%%deprel="i?obj"%%'', or -- equivalently -- ''%%deprel="obj|iobj"%%''), or the keyword's ''deprel'' is ''conj'' (''%%deprel="conj"%%'') and depends on a direct or indirect object (''%%p_deprel="i?obj"%%''), i.e. it is the non-initial conjunct in a coordinated constituent functioning as direct or indirect object. | |
| |
| |
| | <code>[deprel="i?obj" | deprel="conj" & p_deprel="i?obj"]</code> |
| |
| | * [[https://www.korpus.cz/kontext/view?q=~TwkkE2u668ya|This query]] should be used in 13ud, where the ''e_deprel'' attribute is not available. |
| | * Either the keyword's ''deprel'' denotes the direct or indirect object (''%%deprel="i?obj"%%'', or -- equivalently -- ''%%deprel="obj|iobj"%%''), or the keyword's ''deprel'' is ''conj'' (''%%deprel="conj"%%'') and depends on a direct or indirect object (''%%p_deprel="i?obj"%%''), i.e. it is the non-initial conjunct in a coordinated constituent functioning as direct or indirect object. |
| | * In 16ud we get the same result using the ''e_deprel'' attribute in a simpler query: |
| |
| === Proper nouns as subjects, also as conjuncts === | === Proper nouns as subjects, also as conjuncts === |
| * [[https://www.korpus.cz/kontext/view?q=~cuIC4msKMsAW|This query]] finds proper nouns as subjects, including non-initial conjuncts. | * [[https://www.korpus.cz/kontext/view?q=~cuIC4msKMsAW|This query]] finds proper nouns as subjects, including non-initial conjuncts. |
| * Concordances include sentences such as //And what does **Crump** say?// or //“I never even saw her,” said **Pat**.// | * Concordances include sentences such as //And what does **Crump** say?// or //“I never even saw her,” said **Pat**.// |
| | * In 16ud, the same query can be simplified using the ''e_deprel'' attribute: |
| | |
| | <code>[e_deprel="nsubj" & upos="PROPN"]</code> |
| |
| === Gerunds preceded by "with" as the marker === | === Gerunds preceded by "with" as the marker === |
| ===== Description of the list of attributes ===== | ===== Description of the list of attributes ===== |
| |
| * In {{cnk:intercorp:ud_ic_attributes.pdf | Attribute list by language}}, all attributes used in the corpus are listed. | * In {{cnk:intercorp:ud_ic_attributes.pdf | Attribute list by language in 13ud}} or {{cnk:intercorp:ud_ic16ud_attributes.pdf | Attribute list by language in 16ud}} all attributes used in the specific version are listed. |
| * Columns indicate whether the attribute is used for the language specified by the abbreviation in the header. | * Columns indicate whether the attribute is used for the language specified by the abbreviation in the header. |
| * Attributes are divided into four categories, distinguished by background color. | * Attributes are divided into four categories, distinguished by background color. |
| | * For brevity, only linguistically annotated languages are included. E.g. the list for 16ud omits 14 languages denoted by the language codes bn, br, bs, eo, hs, ka, mk, ml, ms, rn, si, sq, th and tl. These languages can be queried Only the ''word'' and ''lc'' attributes can be used to query these languages. |
| |
| ==== Basic attributes ==== | ==== Basic attributes ==== |
| ==== Structural attributes ==== | ==== Structural attributes ==== |
| |
| * These 7 attributes are on the <fc #6495ed>light blue</fc> background. | * These attributes are on the <fc #6495ed>light blue</fc> background. |
| * They extend the reference to the token's syntactic governor (''head'') by additional attributes, making it easier to identify the head and its properties. | * They extend the reference to the token's syntactic governor (''head'') by additional attributes, making it easier to identify the head and its properties. |
| * All attributes of this type are avaliable for all languages. | * All attributes of this type are avaliable for all languages. |
| |
| Daniel Zeman: [[https://lectures.ms.mff.cuni.cz/view.php?rec=421|Reflexives in Universal Dependencies]]. Prague, 04/03/2019. | Daniel Zeman: [[https://lectures.ms.mff.cuni.cz/view.php?rec=421|Reflexives in Universal Dependencies]]. Prague, 04/03/2019. |
| | |
| | ==== About UD-annotated InterCorp ==== |
| | |
| | Olga Nádvorníková (2024): Analyse contrastive de la complexité syntaxique à l’aide de corpus parallèles. Translitteræ, Laboratoire LATTICE (Langues, Textes, Traitements informatiques et Cognition) – CNRS UMR 8094 (Centre national de la recherche scientifique: Unité mixte de recherche), ENS (L'École normale supérieure). Paris, 28/05/2024. [[https://www.youtube.com/watch?v=wJrCez_XPQY|Video]], [[https://jakobson.korpus.cz/~rosen/INTERCORP/SLIDES/C4%20Nadvornikova%20Analyse%20contrastiv%20e%20de%20la%20complexité%20syntaxique.pdf|slides]] |
| | |
| | Alexandr Rosen (2024): Exploring InterCorp v16ud: the potential of a multilingual parallel treebank with complexity and diversity metrics. Instytut Slawistyki Zachodniej i Południowej, Uniwersytet Warszawski. Warszawa, 10/06/2024, [[https://jakobson.korpus.cz/~rosen/INTERCORP/SLIDES/2024_UDCM_Wwa.pdf|slides]]. |
| | |
| | Alexandr Rosen (2023). The InterCorp parallel corpus with a uniform annotation for all languages. Jazykovedný časopis, 74(1):254–265. [[https://www.juls.savba.sk/ediela/jc/2023/1/jc23-01.pdf|Paper]], [[https://jakobson.korpus.cz/~rosen/INTERCORP/SLIDES/rosen-slovko-2023.pdf|slides]]. |
| | |
| | |
| |
