Update README.md
Browse files
README.md
CHANGED
|
@@ -44,7 +44,7 @@ Example:
|
|
| 44 |
```python
|
| 45 |
from transformers import AutoTokenizer, AutoModelForSequenceClassification, pipeline
|
| 46 |
|
| 47 |
-
model_id = "
|
| 48 |
|
| 49 |
classifier = pipeline(
|
| 50 |
"text-classification",
|
|
@@ -71,9 +71,8 @@ The model was fine-tuned on a combined denotational-relation dataset referred to
|
|
| 71 |
|
| 72 |
* ChainNet for metaphor, metonymy, and homonymy relations;
|
| 73 |
* UniMet for additional metonymy examples;
|
| 74 |
-
* WordNet
|
| 75 |
-
|
| 76 |
-
|
| 77 |
These resources use definition or synset-pair information as proxies for relations between word senses.
|
| 78 |
|
| 79 |
## Training Procedure
|
|
@@ -104,23 +103,6 @@ The model was evaluated on:
|
|
| 104 |
|
| 105 |
On the SenseRel denotational dataset, this model achieved the best reported score among the evaluated systems.
|
| 106 |
|
| 107 |
-
## Limitations
|
| 108 |
-
|
| 109 |
-
The model should be used with the following limitations in mind:
|
| 110 |
-
|
| 111 |
-
* It operates on definition pairs, not full diachronic corpus evidence.
|
| 112 |
-
* Training data uses lexical-resource relations as proxies for sense-level semantic change.
|
| 113 |
-
* The distinction between `generalization` and `specialization` is direction-sensitive and depends on the order of the input senses.
|
| 114 |
-
* Taxonomical relations such as `generalization` and `specialization` may be confused with one another.
|
| 115 |
-
* Figurative relations such as `metaphor` and `metonymy` can be difficult to separate, especially when senses are abstract or weakly related.
|
| 116 |
-
* `homonymy` is challenging because the model must distinguish true unrelatedness from distant semantic extension.
|
| 117 |
-
* The model was developed and evaluated for English noun sense definitions; performance may degrade on other parts of speech, languages, domains, or informal text.
|
| 118 |
-
|
| 119 |
-
## Bias, Risks, and Ethical Considerations
|
| 120 |
-
|
| 121 |
-
This model reflects the structure and assumptions of the lexical resources and annotation schemes used for training and evaluation. It may encode biases present in dictionary definitions, lexical databases, and historical semantic descriptions. Its predictions should be treated as linguistic classifications, not as definitive etymological or historical claims.
|
| 122 |
-
|
| 123 |
-
For scholarly use, model outputs should be validated by domain experts, especially when used to support claims about semantic change.
|
| 124 |
|
| 125 |
## Citation
|
| 126 |
|
|
|
|
| 44 |
```python
|
| 45 |
from transformers import AutoTokenizer, AutoModelForSequenceClassification, pipeline
|
| 46 |
|
| 47 |
+
model_id = "ChangeIsKey/denotational-roberta-classifier"
|
| 48 |
|
| 49 |
classifier = pipeline(
|
| 50 |
"text-classification",
|
|
|
|
| 71 |
|
| 72 |
* ChainNet for metaphor, metonymy, and homonymy relations;
|
| 73 |
* UniMet for additional metonymy examples;
|
| 74 |
+
* WordNet for generalization, specialization, and auto-antonymy examples.
|
| 75 |
+
|
|
|
|
| 76 |
These resources use definition or synset-pair information as proxies for relations between word senses.
|
| 77 |
|
| 78 |
## Training Procedure
|
|
|
|
| 103 |
|
| 104 |
On the SenseRel denotational dataset, this model achieved the best reported score among the evaluated systems.
|
| 105 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 106 |
|
| 107 |
## Citation
|
| 108 |
|