LelViLamp commited on
Commit
90886da
1 Parent(s): c18be9e

Upload README.md

Browse files
Files changed (1) hide show
  1. README.md +33 -23
README.md CHANGED
@@ -13,20 +13,16 @@ pretty_name: >-
13
  ---
14
  # OALZ/1788/Q1/NER
15
 
16
- A named entity recognition system (NER) was trained on text extracted from _Oberdeutsche Allgemeine Litteraturueitung_ (OALZ) of the first quarter (January, Febuary, March) of 1788. The scans from which text was extracted can be found at [Bayerische Staatsbibliothek](https://www.digitale-sammlungen.de/de/view/bsb10628753?page=,1) using the extraction strategy of the _KEDiff_ project, which can be found at [`cborgelt/KEDiff`](https://github.com/cborgelt/KEDiff).
17
 
18
- ## Annotations
19
 
20
- Each text passage was annotated in [doccano](https://github.com/doccano/doccano) by two or three annotators and their annotations were cleaned and merged into one dataset. For details on how this was done, see [`LelViLamp/kediff-doccano-postprocessing`](https://github.com/LelViLamp/kediff-doccano-postprocessing). In total, the text consists of about 1.7m characters. The resulting annotation datasets were published on the Hugging Face Hub. There are two versions of the dataset
21
- - [`union-dataset`](https://huggingface.co/datasets/LelViLamp/oalz-1788-q1-ner-annotations-union-dataset) contains the texts split into chunks. This is how they were presented in the annotation application doccano and results from preprocessing step 5a.
22
- - [`merged-union-dataset`](https://huggingface.co/datasets/LelViLamp/oalz-1788-q1-ner-annotations-merged-union-dataset) does not retain this split. The text was merged into one long text and annotation indices were adapted in preprocessing step 5b.
23
 
24
- Note that both these directories contain three equivalent datasets each:
25
- - a Huggingface/Arrow dataset, <sup>*</sup>
26
- - a CSV, <sup>*</sup> and
27
- - a JSONL file.
28
 
29
- <sup>*</sup> The former two should be used together with the provided `text.csv` to catch the context of the annotation. The latter JSONL file contains the full text.
 
30
 
31
  The following categories were included in the annotation process:
32
 
@@ -39,9 +35,16 @@ The following categories were included in the annotation process:
39
  | `PER` | Person | 7,055 | 64,710 | 7 | 9.17 | 9.35 |
40
  | `TIME` | Dates & Time | 1,076 | 13,154 | 8 | 12.22 | 10.98 |
41
 
42
- ## NER models
 
 
 
 
 
43
 
44
- Based on the annotations above, six separate NER classifiers were trained, one for each label type. This was done in order to allow overlapping annotations. For example, in the passage "Dieses Projekt wurde an der Universität Salzburg durchgeführt", you would want to categorise "Universität Salzburg" as an organisation while also extracting "Salzburg" as a location. This would result in an annotation like this:
 
 
45
 
46
  ```json
47
  {
@@ -51,28 +54,33 @@ Based on the annotations above, six separate NER classifiers were trained, one f
51
  }
52
  ```
53
 
54
- Example entry in CSV and Huggingface dataset
55
 
56
- | annotation_id | line_id | start | end | label | label_text | merged |
57
- |:--------------|:-----------|------:|----:|:------|:---------------------|:------:|
58
- | $n$ | example-42 | 28 | 49 | ORG | Universität Salzburg | ??? |
59
- | $n+1$ | example-42 | 40 | 49 | LOC | Salzburg | ??? |
60
 
61
  The columns mean:
62
- - `annotation_id` was assigned internally by enumerating all annotations. This is not present in the JSONL format
63
  - `line_id` is the fragment of the subdivided text, as shown in doccano. Called `id` in the JSONL dataset.
64
  - `start` index of the first character that is annotated. Included, starts with 0.
65
  - `end` index of the last character that is annotated. Excluded, maximum value is `len(respectiveText)`.
66
  - `label` indicates what the passage indicated by $[start, end)$ was annotated as.
67
- - `label_text` contains the text that is annotated by $[start, end)$. This is not present in the JSONL dataset as it can be inferred there.
68
- - `merged` indicates whether this annotation is the result of overlapping annotations of the same label. In that case, `annotation_id` contains the IDs of the individual annotations it was constructed of. This is not present in the JSONL dataset.
 
69
 
70
 
71
- To achieve this overlap, each text passage must be run through all the classifiers individually and each classifier's results need to be combined. For details on how the training was done, see [`LelViLamp/kediff-ner-training`](https://github.com/LelViLamp/kediff-ner-training).
 
 
 
 
72
 
73
  The [`dbmdz/bert-base-historic-multilingual-cased`](https://huggingface.co/dbmdz/bert-base-historic-multilingual-cased) tokeniser was used to create historical embeddings. Therefore, it is necessary to use that in order to use these NER models.
74
 
75
- The models' performance measures are as follows:
76
 
77
  | Model | Selected Epoch | Checkpoint | Validation Loss | Precision | Recall | F<sub>1</sub> | Accuracy |
78
  |:-------------------------------------------------------------------|:--------------:|-----------:|----------------:|----------:|--------:|--------------:|---------:|
@@ -83,5 +91,7 @@ The models' performance measures are as follows:
83
  | [`PER`](https://huggingface.co/LelViLamp/oalz-1788-q1-ner-per) | 2 | `2786` | .059186 | .914037 | .849048 | .879070 | .983253 |
84
  | [`TIME`](https://huggingface.co/LelViLamp/oalz-1788-q1-ner-time) | 1 | `1393` | .016120 | .866866 | .724958 | .783099 | .994631 |
85
 
 
 
86
  ## Acknowledgements
87
- The data set and models were created in the project _Kooperative Erschließung diffusen Wissens_ ([KEDiff](https://uni-salzburg.elsevierpure.com/de/projects/kooperative-erschließung-diffusen-wissens-ein-literaturwissenscha)), funded by the [State of Salzburg](https://salzburg.gv.at), Austria 🇦🇹, and carried out at [Paris Lodron Universität Salzburg](https://plus.ac.at).
 
13
  ---
14
  # OALZ/1788/Q1/NER
15
 
16
+ A named entity recognition system (NER) was trained on text extracted from _Oberdeutsche Allgemeine Litteraturzeitung_ (OALZ) of the first quarter (January, Febuary, March) of 1788. The scans from which text was extracted can be found at [Bayerische Staatsbibliothek](https://www.digitale-sammlungen.de/de/view/bsb10628753?page=,1). The extraction strategy of the _KEDiff_ project can be found at [`cborgelt/KEDiff`](https://github.com/cborgelt/KEDiff).
17
 
 
18
 
 
 
 
19
 
20
+ ## Annotations
21
+
22
+ Each text passage was annotated in [doccano](https://github.com/doccano/doccano) by two or three annotators and their annotations were cleaned and merged into one dataset. For details on how this was done, see [`LelViLamp/kediff-doccano-postprocessing`](https://github.com/LelViLamp/kediff-doccano-postprocessing). In total, the text consists of about 1.7m characters. The resulting annotation datasets were published on the Hugging Face Hub. There are two versions:
 
23
 
24
+ - [`union-dataset`](https://huggingface.co/datasets/LelViLamp/oalz-1788-q1-ner-annotations-union-dataset) contains the texts split into chunks. This is how they were presented in the annotation application doccano. This dataset is the result of preprocessing step 5a.
25
+ - [`merged-union-dataset`](https://huggingface.co/datasets/LelViLamp/oalz-1788-q1-ner-annotations-merged-union-dataset) does not retain this split. The text was merged into one long text and annotation, indices were adapted in preprocessing step 5b.
26
 
27
  The following categories were included in the annotation process:
28
 
 
35
  | `PER` | Person | 7,055 | 64,710 | 7 | 9.17 | 9.35 |
36
  | `TIME` | Dates & Time | 1,076 | 13,154 | 8 | 12.22 | 10.98 |
37
 
38
+ ### Data format
39
+
40
+ Note that there is three versions of the dataset:
41
+ - a Huggingface/Arrow dataset,
42
+ - a CSV, and
43
+ - a JSONL file.
44
 
45
+ The former two should be used together with the provided `text.csv` to catch the context of the annotation. The latter JSONL file contains the full text.
46
+
47
+ The **JSONL file** contains lines of this format:
48
 
49
  ```json
50
  {
 
54
  }
55
  ```
56
 
57
+ And here are some example entries as used in the CSV and Huggingface dataset:
58
 
59
+ | `annotation_id` | `line_id` | `start` | `end` | `label` | `label_text` | `merged` |
60
+ |:----------------|:-----------|--------:|------:|:--------|:---------------------|:--------:|
61
+ | $n$ | example-42 | 28 | 49 | ORG | Universität Salzburg | ??? |
62
+ | $n+1$ | example-42 | 40 | 49 | LOC | Salzburg | ??? |
63
 
64
  The columns mean:
65
+ - `annotation_id` was assigned internally by enumerating all annotations in the original dataset, which is not published. This value is not present in the JSONL file.
66
  - `line_id` is the fragment of the subdivided text, as shown in doccano. Called `id` in the JSONL dataset.
67
  - `start` index of the first character that is annotated. Included, starts with 0.
68
  - `end` index of the last character that is annotated. Excluded, maximum value is `len(respectiveText)`.
69
  - `label` indicates what the passage indicated by $[start, end)$ was annotated as.
70
+ - `label_text` contains the text that is annotated by $[start, end)$. This is not present in the JSONL dataset as it can be inferred from the `text` entry there.
71
+ - `merged` indicates whether this annotation is the result of overlapping annotations of the same label. In that case, `annotation_id` contains the IDs of the individual annotations it was constructed of, separated by underscores. This value is not present in the JSONL dataset, and this column is redundant, as it can be inferred from `annotation_id`.
72
+
73
 
74
 
75
+ ## NER models
76
+
77
+ Based on the annotations above, six separate NER classifiers were trained, one for each label type. This was done in order to allow overlapping annotations. For example, in the passage "Dieses Projekt wurde an der Universität Salzburg durchgeführt", you would want to categorise "Universität Salzburg" as an organisation while also extracting "Salzburg" as a location.
78
+
79
+ To achieve this overlap, each text passage must be run through all the classifiers individually and each classifier's results need to be combined. For details on how the training was done and examples of inference time, see [`LelViLamp/kediff-ner-training`](https://github.com/LelViLamp/kediff-ner-training).
80
 
81
  The [`dbmdz/bert-base-historic-multilingual-cased`](https://huggingface.co/dbmdz/bert-base-historic-multilingual-cased) tokeniser was used to create historical embeddings. Therefore, it is necessary to use that in order to use these NER models.
82
 
83
+ The models' performance measures are shown in the following table. Click the model name to find the model on the Huggingface Hub.
84
 
85
  | Model | Selected Epoch | Checkpoint | Validation Loss | Precision | Recall | F<sub>1</sub> | Accuracy |
86
  |:-------------------------------------------------------------------|:--------------:|-----------:|----------------:|----------:|--------:|--------------:|---------:|
 
91
  | [`PER`](https://huggingface.co/LelViLamp/oalz-1788-q1-ner-per) | 2 | `2786` | .059186 | .914037 | .849048 | .879070 | .983253 |
92
  | [`TIME`](https://huggingface.co/LelViLamp/oalz-1788-q1-ner-time) | 1 | `1393` | .016120 | .866866 | .724958 | .783099 | .994631 |
93
 
94
+
95
+
96
  ## Acknowledgements
97
+ The data set and models were created in the project _Kooperative Erschließung diffusen Wissens_ ([KEDiff](https://uni-salzburg.elsevierpure.com/de/projects/kooperative-erschließung-diffusen-wissens-ein-literaturwissenscha)), funded by the [State of Salzburg](https://salzburg.gv.at), Austria, and carried out at [Paris Lodron Universität Salzburg](https://plus.ac.at). 🇦🇹