The Corpus Thread - Det Danske Sprog- og Litteraturselskab

More documents

Recommendations

Info

7.2. The ePOS tag set for Danish 142 responding, unambiguous tag is assigned. Tags outside this strictly inflectional scope, e.g. on syntax, semantics, or morphological composition of lemmas, are currently not provided. As the tagger is trained on the Danish PAROLE Corpus, the tag set of the ePOS tagger will be based on that one used by PAROLE (see Keson (1998a) and Keson (1998b)), however with some modifications, some of them as a consequence of the modified token concept, cf. Section 7.1.2, some of them for simplification reasons in order to hopefully achieve a better language model. The ePOS tagger utilizes a full-form lexicon that is compiled from the following three resources: ⊲ An existing full-form lexicon derived from an earlier version of The Danish Dictionary: FLEXIKON. ⊲ The freely available FLEXION lexicon established by Ole Norling- Christensen and others. 4 ⊲ A supplementary lexicon derived from the tagged PAROLE material. The ePOS full-form lexicon is described more in-depth in Chapter 8. 7.2.1 Tag structure The PAROLE tag set is positional which means that within a tag a certain inflectional marker is always found at a fixed position in a sequence of markers making up the tag. For example, in the case of nouns, the gender marker is always found at position 3, number at position 4, case at position 5, and definiteness at position 8. However, the positional system is dependent on the POS in question: In the case of verbs, which also may carry nominal inflectional markers, definiteness is still at position 8, but gender is at 4, number at 6, and case at 11. These varying positions would make it very cumbersome later on to perform corpus queries of the type find all words that are marked for case = “genitive” no matter what their POS is. The ePOS tag set therefore favors fixed, POS-independent marker positions. In contrast to ePOS and PAROLE, the tag set applied by FLEXIKON and ONCLEX is a compact tag set that leaves out non-applicable and implicit information. Hence, it is easy to decode for humans, but may be difficult to formulate complex morphological corpus queries on. Therefore, the tag 4 Called ONCLEX in the following to better distinguish it from FLEXIKON. ONCLEX can be downloaded from: http://korpus.dsl.dk/e-resurser/boejningsformer_download.php?lang=en
7.2. The ePOS tag set for Danish 143 sets of these sources needs to be converted into a positional one with fixed marker positions independent of the POS in question. 5 The basic structure of an ePOS tag is: CLASS:nominal:verbal:additional where CLASS is a two-character POS classifier comprising a POS indicator (first character) and a sub-classifier. The first colon indicates the boundary between the CLASS part and the inflectional part of the tag. Here, nominal and verbal are strings of markers concerning nominal and verbal morphological information respectively. The additional string carries further markers relevant to adjectives, some adverbs, and pronouns. Marker strings have fixed lengths – nominal 4, verbal 2, and additional 4. Each marker in such a string is represented by one character. The three groups of morphological markers are separated by colons (:). A morphological marker which is irrelevant to a certain paradigm is marked with a dash (-) at the respective position(s) of the tag. In cases where inflectional markers are underspecified, this is indicated by a hash sign (#) at the respective position(s), meaning any value of this category. In certain cases PAROLE applies tags that are underspecified beyond the level of underspecification that the ePOS tag set envisages. Instead of disambiguating these tags in the PAROLE corpus prior to using it as a source for the language model of the tagger, they have been adopted by ePOS. In these cases, underspecified markers are marked with a section sign (§). In order to further adapt PAROLE to ePOS, the ePOStagged version of PAROLE should be examined and §-underspecifications should be manually disambiguated. The applied markers in ePOS reflect the choices made in PAROLE, cf. its documentation (Keson (1998a) or Keson (1998b)). Nominal markers The string of nominal markers is of length four, it carries the following markers: 1. Number: singular (s) or plural (p) 2. Definiteness: indefinite (i) or definite (d) 3. Case: unmarked (u), genitive (g), or fossilized (f), and – for personal pronouns only – nominative (n) (accusative is identical with unmarked in these cases and tagged withu) 5 The CST tag set used in the CST tagger (see Section 6.2.2), which is also based on PA- ROLE (and seems in part to silently utilize ONCLEX as well), applies compact tags too, cf. the description of the CST tag set at ⊲ http://cst.dk/online/pos_tagger/rapport/bilag/tagset.html. The same applies to the VISL tag set.
Page 1 and 2:
The Corpus Thread “Reference corp
Page 3 and 4:
Chapter 1 Aim and concepts Sketchin
Page 5 and 6:
1.1. Aim of the project 5 Metadata
Page 7 and 8:
1.2. Project tasks and documentatio
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
1.3. Text collection, text bank, co
Page 15 and 16:
Chapter 2 The text bank A platform
Page 17 and 18:
2.2. Implementation 17 and metadata
Page 19 and 20:
Chapter 3 Text metadata What the he
Page 21 and 22:
3.1. Concepts 21 Section 3.3 starts
Page 23 and 24:
3.2. Header structure 23 (file des
Page 25 and 26:
3.2. Header structure 25 great verb
Page 27 and 28:
3.2. Header structure 27 The follow
Page 29 and 30:
3.2. Header structure 29 deprecated
Page 31 and 32:
3.2. Header structure 31 the text i
Page 33 and 34:
3.2. Header structure 33 Another el
Page 35 and 36:
3.2. Header structure 35 appDesc
Page 37 and 38:
3.2. Header structure 37 informal p
Page 39 and 40:
3.2. Header structure 39 3.2.3.4 Te
Page 41 and 42:
3.3. Filling in the header 41 revi
Page 43 and 44:
3.3. Filling in the header 43 samp
Page 45 and 46:
3.3. Filling in the header 45 and 9
Page 47 and 48:
3.3. Filling in the header 47 descr
Page 49 and 50:
3.3. Filling in the header 49 ⊲ a
Page 51 and 52:
3.3. Filling in the header 51 Legal
Page 53 and 54:
3.3. Filling in the header 53 ⊲ a
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
3.3. Filling in the header 61 Value
Page 63 and 64:
Page 65 and 66:
3.3. Filling in the header 65 ⊲ p
Page 67 and 68:
3.3. Filling in the header 67 Prope
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
3.3. Filling in the header 83 3.3.3
Page 85 and 86:
4.1. Basic considerations 85 Outlin
Page 87 and 88:
4.2. Formatting text 87 russiske hi
Page 89 and 90:
4.2. Formatting text 89 Mirganjan
Page 91 and 92: 4.2. Formatting text 91 udvikle ude
Page 93 and 94: 4.2. Formatting text 93 4.2.3.4 Add
Page 95 and 96: 4.2. Formatting text 95 i dag . T
Page 97 and 98: Part III Collecting 97
Page 99 and 100: 5.1. Implementation 99 5.5.2 Implem
Page 101 and 102: 5.1. Implementation 101 [request c
Page 103 and 104: 5.2. Header constructor:make-header
Page 115 and 116: 5.3. Pre-tokenizer:pretokenize 115
Page 117 and 118: 5.3. Pre-tokenizer:pretokenize 117
Page 119 and 120: 5.4. Text id registry:register-text
Page 121 and 122: 5.4. Text id registry:register-text
Page 123 and 124: 5.5. id dispatcher:make-id 123 0 11
Page 125 and 126: Part IV Markup 125
Page 127 and 128: 6.1. Requirements 127 Outline of th
Page 129 and 130: 6.2. Survey 129 1. IMS’s TreeTagg
Page 131 and 132: 6.2. Survey 131 Code: Java. Assessm
Page 133 and 134: 6.2. Survey 133 9. alias-i’s Ling
Page 135 and 136: 6.3. Case study 135 lemmatization c
Page 137 and 138: 6.4. Further reading 137 disambigua
Page 139 and 140: 7.1. Modifications of the PAROLE Co
Page 141: 7.2. The ePOS tag set for Danish 14
Page 145 and 146: 7.2. The ePOS tag set for Danish 14
Page 153 and 154: Chapter 8 The full-form lexicon Sam
Page 155 and 156: 8.1. Enhancing existing material 15
Page 157 and 158: 8.1. Enhancing existing material 15
Page 159 and 160: Part V Deployment 159
Page 161 and 162: 9.2. Text material 161 Type Source
Page 163 and 164: 10.2. Funktionaliteter 163 2. The u
Page 165 and 166: 10.2. Funktionaliteter 165 fortolke
Page 167 and 168: 10.2. Funktionaliteter 167 teknolog
Page 169 and 170: 10.2. Funktionaliteter 169 Implemen
Page 171 and 172: 10.2. Funktionaliteter 171 forbinde
Page 173 and 174: 10.2. Funktionaliteter 173 10.2.9 K
Page 175 and 176: Bibliography Andersen, M. S., Asmus
show all

The Corpus Thread - Det Danske Sprog- og Litteraturselskab

Create successful ePaper yourself

Delete template?

Save as template?