User Tools

Site Tools


02_browsing:04_queries:04_combined

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
02_browsing:04_queries:04_combined [2022/01/06 15:04]
Simone Ueberwasser
02_browsing:04_queries:04_combined [2022/06/27 09:21] (current)
Line 15: Line 15:
   - To find //io// written by males, we query for: ''tok="io" & meta::sex="M"''. That reads as: a token with the contents //io// and the gender //m//   - To find //io// written by males, we query for: ''tok="io" & meta::sex="M"''. That reads as: a token with the contents //io// and the gender //m//
   - In the second example we are looking for different spelling variants for the standard spelling //was//. We can find these forms as a relative pronoun by using the normalized [[02_browsing:02_layers|layers]] and the [[03_processing:06_pos|PoS annotation]]. In the normalized layer, we are looking for the spelling form //was// regardless of the original respresentation. In the PoS annotation we look for a relative pronoun. This results in the query: ''tok="was" & pos="PRELS" & #1 _=_ #2''. We can translate that as: the token has to be //was// and the PoS-Annotation has to be //PRELS// and the two annotations have to be found on the same token //#1 _=_ #2//. Please keep in mind that this is the syntax for subcorpora tagged with TreeTagger. The RFTagger uses a more precise annotation for relative pronouns, e.g. PRO.Rel.Subst.Nom.Sg.Neut. The query would thus look like: ''tok="was" & pos=/PRO.Rel.*/ & #1 _=_ #2''.   - In the second example we are looking for different spelling variants for the standard spelling //was//. We can find these forms as a relative pronoun by using the normalized [[02_browsing:02_layers|layers]] and the [[03_processing:06_pos|PoS annotation]]. In the normalized layer, we are looking for the spelling form //was// regardless of the original respresentation. In the PoS annotation we look for a relative pronoun. This results in the query: ''tok="was" & pos="PRELS" & #1 _=_ #2''. We can translate that as: the token has to be //was// and the PoS-Annotation has to be //PRELS// and the two annotations have to be found on the same token //#1 _=_ #2//. Please keep in mind that this is the syntax for subcorpora tagged with TreeTagger. The RFTagger uses a more precise annotation for relative pronouns, e.g. PRO.Rel.Subst.Nom.Sg.Neut. The query would thus look like: ''tok="was" & pos=/PRO.Rel.*/ & #1 _=_ #2''.
-  - In the third example we look for two tokens, one directly following the other. Here, we could use one of the normalisations, too, i.e. ''gloss''  or we could use the token. This choice depends on what we want to find. If we are after the spelling //est-ce que// used by the informant, we query for ''tok=/.../''. If, on the other hand, we want to include unconventional spellings like //sq//, we have to use ''gloss=/.../''. Let us use the first option, which gives us the following query: ''tok="est-ce" & tok="que" & #1 . #2'', which we can read as: a first token //est-ce// and a second token //que//. The expression ''#1 . #2'' means the first token has to directly precede the second one.+  - In the third example we look for two tokens, one directly following the other. Here, we could use one of the normalisations, too, i.e. ''gloss''  or we could use the token. This choice depends on what we want to find. If we want to after the spelling //est-ce que// used by the informant, we query for ''tok=/.../''. If, on the other hand, we want to include unconventional spellings like //sno//, we have to use ''gloss=/.../''. Let us use the first option, which gives us the following query: ''pos="PRO:pers" & tok="sono" & #1 . #2'', which we can read as: a first token has to be a personal pronound and a second one has to be //sono//. The expression ''#1 . #2'' means the first token has to directly precede the second one.
  
-That much for the examples. But how can you remember all of these options? You do not have to, since ANNIS offers you lots of [[02_browsing:04_queries:01_support|support in creation the queries]].+That much for the examples. But how can you remember all of these options? You do not have to, since ANNIS offers you lots of [[02_browsing:05_support|support in creation the queries]].
02_browsing/04_queries/04_combined.1641477872.txt.gz · Last modified: 2022/06/27 09:21 (external edit)