The Corpus Thread - Det Danske Sprog- og Litteraturselskab

More documents

Recommendations

Info

Chapter 6 Survey of POS taggers Approaches to making words tell who they are Deliverables concerned D10 Lemmatizer It is considered indispensable that corpus texts need to indicate the lemma form of each inflected word form in the corpus to let the user of the corpus perform more flexible queries. Therefore, it is necessary to either develop or configure a lemmatizer (that may be based on a full-form lexicon or a morphological analyzer). In the context of WP 2.1, a lemmatizer designed as an integral part of a POS tagger is the preferable solution. Outcome: Tool with documentation. D11 POS tagger In order to tag tokens in corpus texts with part-of-speech information, it is necessary to either develop or configure a POS tagger (either based on a full-form lexicon or a morphological analyzer) and a suitable tag set. Outcome: Tool with documentation. 126
6.1. Requirements 127 Outline of this chapter This chapter describes WP 2.1’s requirements to part-of-speech (= POS) tagging and provides a survey of existing POS approaches and their suitability. The survey is based on the requirements defined in Section 6.1. The chapter finishes with some conclusions on which approach to choose for tagging WP 2.1 corpus texts. 6.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 127 6.2 Survey . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 6.2.1 Universal taggers . . . . . . . . . . . . . . . . . . 128 6.2.2 Taggers for Danish . . . . . . . . . . . . . . . . . 133 6.2.3 Conclusions . . . . . . . . . . . . . . . . . . . . . 134 6.3 Case study . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 6.3.1 Building a token-based HMM . . . . . . . . . . . 135 6.3.2 Building a lexicon-based HMM . . . . . . . . . . 136 6.4 Further reading . . . . . . . . . . . . . . . . . . . . . . . . 137 6.1 Requirements Within a narrow DK-CLARIN context, the process of POS tagging could be reduced to just letting some kind of black box perform what is needed in order to get the text material of this corpus work-package marked-up with appropriate morphosyntactic info. Seen in this is light, the major requirement would be precision, therefore the only relevant answer allowed to ask on this topic may seem: How close to 100 % do we get? However, precision is not a quality in itself but the result of other properties. As a black box is not configurable, and as requirements definitely will change over time and beyond the narrow scope of the DK-CLARIN project, “close to 100 %” may not be that close once some of the prerequisites of the tagging scenario have been modified. Therefore, an open configurable solution seems to be a more forward-looking approach. Open means that both the tagger software itself and its linguistic ‘knowledge’ must be open source and thus configurable, and available for free for everybody. Open source and free availability is considered a major requirement and crucial in order to achieve a permanent level of high precision. A secondary requirement is that the tagger should not just apply a model of the language in question, i.e. Danish, and assign appropriate POS tags to words, but also perform lemmatization, i.e. assign the base forms of all (inflected) words. As a consequence of that, the tagger should apply an open-
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:
3.3. Filling in the header 71 Value
Page 73 and 74:
Page 75 and 76: 3.3. Filling in the header 75 Legal
Page 81 and 82: 3.3. Filling in the header 81 Value
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: Part IV Markup 125
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 and 142: 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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?