> For the complete documentation index, see [llms.txt](https://tracer.gitbook.io/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tracer.gitbook.io/manual/manual/pos-tagging-lemmatisation-and-wordnets.md).

# PoS-tagging, lemmatisation & WordNets

In order to detect text reuse, TRACER also requires linguistic information pertaining to the language you're examining. These are:

### A *lemma* file...

...listing all word-forms present in the text, their base-form and word-class or part-of-speech tag. This information can be automatically extracted using a morphological analyser that is able to read the language you wish to analyse.

The output file produced by your morphological analyser of choice needs to be converted to TRACER's input format. TRACER takes three columns, separated by `TAB`s: a column listing the *word-forms* as they appear in the text; a column providing the *base-form* or dictionary entry of every word-form; and a third column with the relative *word-class* (verb, noun, etc.):

![This TAB-separated three-column .txt file contains information TRACER needs in order to detect text reuse in Latin texts.](https://1711629118-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LAMSxaPS1y_QM9B-H1t%2F-LAO3QI0Yx8gIaVvKMgH%2F-LAO3WdR-Zfc31B3P8gk%2Flemma-file.png?generation=1524060267708051\&alt=media)

### a *synonyms* file...

...listing all dictionary entries for your particular language along with their synonyms. In other words, a thesaurus. You can extract these lists from [wordnets](http://globalwordnet.org/wordnets-in-the-world/) if available for the language you are working with. While wordnets typically display this information as `lemma synonym1, synonyms2, synonym3, ...` (one line per lemma), TRACER requires a bidirectional two-column list, such as:

![This TAB-separated two-column .txt file contains information TRACER needs in order to detect looser forms of text reuse in Latin texts, such as paraphrase. The left column contains the base-form or lemma and the right column one of its synonyms.](https://1711629118-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LAMSxaPS1y_QM9B-H1t%2F-LAO3QI0Yx8gIaVvKMgH%2F-LAO3WeNuKDy1FHQ_fBB%2Fsyns-file.png?generation=1524060270595335\&alt=media)

The figure above displays one synonym per lemma. For lemmas with multiple synonyms the file should be structured as follows:

```
lemma1   synonym1
lemma1   synonym2
lemma1   synonym3
```

And should be bidirectional:

```
lemma1      synonym1
synonym 1   lemma 1
```

**If you wish to detect non-verbatim text reuse (e.g. paraphrase) you need *****both***** the lemma and the synonyms files. If you're only interested in word-for-word text reuse, you don't need the lemma and synonym files.**\
The `.txt`, `.lemma` and, optionally, the `.synonyms` files must be deposited in TRACER's `corpora` directory and declared in the `tracer_config.xml` file, as shown below.

![The path of the input files must be specified in the tracer\_config.xml file.](https://1711629118-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LAMSxaPS1y_QM9B-H1t%2F-LAO3QI0Yx8gIaVvKMgH%2F-LAO3WhUZYM1LeQOsfv1%2Fpath.png?generation=1524060270060801\&alt=media)

If you don't use a `.syns` file, you needn't delete the `SYNONYMS_FILE_NAME` property but must declare this in the *Word-level Preprocessing* section of TRACER's configuration file.

##