Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
en:eebo:multiword [2016/09/28 15:19] – veronikapojarova | en:eebo:multiword [2016/11/11 07:56] – [Searching the corpus] kristinavalentinyova |
---|
====== Lesson 8: Multiword searches====== | ====== Lesson 8: Multiword searches====== |
In the Early Modern English period, there were two different ways of marking the perfect tenses. In the present day, the auxiliary //have// is used for example in the present perfect, as in //It has come to my attention//. However, as late as the eighteenth century, the perfect tenses could be marked with the auxiliary //to be//. These two markings were more or less in complementary distribution, i.e. they were used with different types of verbs. According to the [[http://public.oed.com/aspects-of-english/english-in-time/grammar-in-early-modern-english/|OED ]], //to be// was the preferred way of forming the perfect verbs of motion, while //to have// was used in most other cases. Shakespeare normally uses the auxiliary //to be// with //creep, enter, flee, go, meet, retire, ride, and run//. | In the Early Modern English period, there were two different ways of marking the perfect tense. In the present day, the auxiliary //have// is used to form the present perfect, as in //It has come to my attention//. However, as late as the eighteenth century, the perfect tenses could be marked with the auxiliary //to be//. These two markings were more or less in complementary distribution, i.e. they were used with different types of verbs. According to the [[http://public.oed.com/aspects-of-english/english-in-time/grammar-in-early-modern-english/|OED ]], //to be// was the preferred way of forming the perfect verbs of motion, while //to have// was used in most other cases. Shakespeare normally uses the auxiliary //to be// with //creep, enter, flee, go, meet, retire, ride, and run//. |
| |
====== Searching the corpus ====== | ====== Searching the corpus ====== |
| |
If searching for one specific form such as //is arrived//, we may use the [[en:manualy:kontext:novy_dotaz|basic query]] as described in our [[en:eebo:first_query|first lesson ]]. | If searching for one specific form such as //is arrived//, we may use the //Phrase// query type as described in our [[en:eebo:first_query|first lesson ]]. |
| |
However, in this case we want to find all the possible variants, //am come//, //are come// the query can be written in [[en:pojmy:dotazovaci_jazyk|CQL]] (Corpus Query Language) using a number of regular expressions. Furthermore, the CQL query mode in the [[en:kontext| KonText]] interface is case sensitive, and therefore both variants should be included in the query in order for us to obtain as many relevant hits as possible. | However, in this case we want to find all the possible variants, //am come//, //are come// the query can be written in [[en:pojmy:dotazovaci_jazyk|CQL]] (Corpus Query Language) using a number of regular expressions. Furthermore, the CQL query mode in the [[en:kontext| KonText]] interface is case sensitive, and therefore both variants should be included in the query in order for us to obtain as many relevant hits as possible. |
''([word="am"]|[word="are"]|[word="is"])[word="arrived"]'' | ''([word="am"]|[word="are"]|[word="is"])[word="arrived"]'' |
| |
If we want the search to include both variants, i.e. //be// and //have//, we can include all of the possible forms in the query. Furthermore, we want to include all the possible spelling variants (see our [[en:eebo:orthography_spelling|second lesson]]). The final query could look like this: | If we want the search to include both variants, i.e. //be// and //have//, we can include all of the possible forms in the query. Furthermore, we want to include all the possible spelling variants (see [[en:eebo:orthography_spelling|Lesson Two]]). The final query could look like this: |
| |
''([word="am"]|[word="are"]|[word="[iy]s"]|[word="has"]|[word="ha[uv]e"])[word="ar?ri[uv]ed"]'' | ''([word="am"]|[word="are"]|[word="[iy]s"]|[word="has"]|[word="ha[uv]e"])[word="ar?ri[uv]ed"]'' |
| |
<WRAP round tip 50%> | //Frequency -> Node forms// provides a listing of all types found with the given query in order of frequency. Below are the results of the search viewed as node forms. |
Remember that the construction //to be + past participle// is also used as a means of expressing passive voice. This difficulty does not arise with //arrive//, we must be careful when searching for transitive verbs. | |
</WRAP> | |
| |
After consulting an etymological dictionary and also based on our previous experience, we know that we may expect forms such as //diuine//, //deuine//, //dywine//, and //divinne// (among many others). The vowel can be either //e//, //i// or //y//, which is simplified as ''[eiy]''. The same is true of the set ''[uvw]''. The form always contains at least one nasal //n//, while the second is only optional (indicated by the question mark). The final silent //e// is also optional. The resulting query should look like this: | {{:en:eebo:eebo_pic_08.png?direct&300 |}} |
| |
''[word="[dD][eiy][uvw][iy]nn?e?"]'' | By selecting the positive filter, we can view the node forms individually, e.g. all the instances of //have arrived//. Alternately, we can conduct a separate search for all the variants with the auxiliary //have// and all those with the auxiliary //be//. |
| |
Frequency -> Node forms provides a listing of all types found with the given query in order of frequency. | A number of things can be done at this stage, including a survey of the i.p.m. by period. |
| |
//EEBO_pic02.png // | //Frequency → Text Types// on the menu bar shows us a list of frequencies by period and by decade. By default, the results are ordered by frequency. By clicking on the text doc.decade we can order the results chronologically. |
| |
A similar example is with the word //godly//: | [[en:eebo:competing_forms|Lesson Three]] gives an example of how such data could be converted into a graph. |
| |
''Godly: [word="[gG]oo?dle?[yi]c?k?e?"]'' | |
| |
This query returns not only the frequent forms //godly, goodly, godlie, godlye// and //goodlye//, but also much less frequent (and much less anticipated) variants such as //godlyc// and even //godlycke//. In the latter we can observe remnants of the Old English adjectival suffixes <-līc> and <-līce>. | |
| |
| <WRAP round tip 50%> |
| Remember that the construction //to be + past participle// is also used as a means of expressing passive voice. This difficulty does not arise with //arrive//, we must keep the possibility in mind when searching for transitive verbs. In the case of a verb such as //enter//, where the phrase //is entered// can potentially have both the perfect and passive meanings, there is unfortunately not much we can do to eliminate the undesired variant. |
| Another complication arises from the use of the participle as adjective, for example //I am ashamed of...// |
| </WRAP> |
| |
=== Task: Spelling variants === | |
| |
| === Task: Verbs of motion === |
| |
<WRAP round help 50%> | <WRAP round help 50%> |
* Find as many spelling variants of the word //royal// as possible | * Search for the auxiliaries used with //come// and //go// |
* Keep in mind the spelling conventions and irregularities mentioned above | * Are there any developments over the course of the Early Modern period? |
| * Keep in mind the spelling conventions and irregularities mentioned in Lesson 2 |
* Make sure that the Query type is set to CQL | * Make sure that the Query type is set to CQL |
</WRAP> | </WRAP> |