2017-04-15 13:05:47 +03:00
|
|
|
# coding: utf8
|
|
|
|
from __future__ import unicode_literals
|
2019-10-01 22:36:04 +03:00
|
|
|
|
2019-05-04 19:16:03 +03:00
|
|
|
from collections import OrderedDict
|
2015-08-27 10:16:11 +03:00
|
|
|
|
2019-09-11 15:00:36 +03:00
|
|
|
from .symbols import NOUN, VERB, ADJ, PUNCT, PROPN
|
2019-10-01 22:36:04 +03:00
|
|
|
from .errors import Errors
|
|
|
|
from .lookups import Lookups
|
2020-05-20 10:56:56 +03:00
|
|
|
from .parts_of_speech import NAMES as UPOS_NAMES
|
2015-08-27 10:16:11 +03:00
|
|
|
|
2014-12-23 07:16:57 +03:00
|
|
|
|
|
|
|
class Lemmatizer(object):
|
2019-03-08 13:42:26 +03:00
|
|
|
"""
|
|
|
|
The Lemmatizer supports simple part-of-speech-sensitive suffix rules and
|
|
|
|
lookup tables.
|
|
|
|
|
|
|
|
DOCS: https://spacy.io/api/lemmatizer
|
|
|
|
"""
|
|
|
|
|
2015-08-27 10:16:11 +03:00
|
|
|
@classmethod
|
2019-10-01 22:36:04 +03:00
|
|
|
def load(cls, *args, **kwargs):
|
|
|
|
raise NotImplementedError(Errors.E172)
|
|
|
|
|
2020-07-09 23:11:24 +03:00
|
|
|
def __init__(self, lookups, is_base_form=None, *args, **kwargs):
|
2019-10-01 22:36:04 +03:00
|
|
|
"""Initialize a Lemmatizer.
|
2014-12-23 07:16:57 +03:00
|
|
|
|
2019-10-01 22:36:04 +03:00
|
|
|
lookups (Lookups): The lookups object containing the (optional) tables
|
|
|
|
"lemma_rules", "lemma_index", "lemma_exc" and "lemma_lookup".
|
|
|
|
RETURNS (Lemmatizer): The newly constructed object.
|
|
|
|
"""
|
|
|
|
if args or kwargs or not isinstance(lookups, Lookups):
|
|
|
|
raise ValueError(Errors.E173)
|
|
|
|
self.lookups = lookups
|
2020-06-29 15:16:57 +03:00
|
|
|
self.is_base_form = is_base_form
|
2015-08-25 16:46:19 +03:00
|
|
|
|
2016-12-07 23:12:49 +03:00
|
|
|
def __call__(self, string, univ_pos, morphology=None):
|
2019-10-01 22:36:04 +03:00
|
|
|
"""Lemmatize a string.
|
|
|
|
|
|
|
|
string (unicode): The string to lemmatize, e.g. the token text.
|
|
|
|
univ_pos (unicode / int): The token's universal part-of-speech tag.
|
|
|
|
morphology (dict): The token's morphological features following the
|
|
|
|
Universal Dependencies scheme.
|
|
|
|
RETURNS (list): The available lemmas for the string.
|
|
|
|
"""
|
|
|
|
lookup_table = self.lookups.get_table("lemma_lookup", {})
|
|
|
|
if "lemma_rules" not in self.lookups:
|
|
|
|
return [lookup_table.get(string, string)]
|
2020-05-20 10:56:56 +03:00
|
|
|
if isinstance(univ_pos, int):
|
|
|
|
univ_pos = UPOS_NAMES.get(univ_pos, "X")
|
|
|
|
univ_pos = univ_pos.lower()
|
|
|
|
|
|
|
|
if univ_pos in ("", "eol", "space"):
|
2018-03-27 20:23:02 +03:00
|
|
|
return [string.lower()]
|
2016-09-27 14:52:11 +03:00
|
|
|
# See Issue #435 for example of where this logic is requied.
|
2020-06-29 15:16:57 +03:00
|
|
|
if callable(self.is_base_form) and self.is_base_form(univ_pos, morphology):
|
2018-03-27 20:23:02 +03:00
|
|
|
return [string.lower()]
|
2019-10-01 22:36:04 +03:00
|
|
|
index_table = self.lookups.get_table("lemma_index", {})
|
|
|
|
exc_table = self.lookups.get_table("lemma_exc", {})
|
|
|
|
rules_table = self.lookups.get_table("lemma_rules", {})
|
2020-05-20 16:35:08 +03:00
|
|
|
if not any((index_table.get(univ_pos), exc_table.get(univ_pos), rules_table.get(univ_pos))):
|
|
|
|
if univ_pos == "propn":
|
|
|
|
return [string]
|
|
|
|
else:
|
|
|
|
return [string.lower()]
|
2019-10-01 22:36:04 +03:00
|
|
|
lemmas = self.lemmatize(
|
💫 Tidy up and auto-format .py files (#2983)
<!--- Provide a general summary of your changes in the title. -->
## Description
- [x] Use [`black`](https://github.com/ambv/black) to auto-format all `.py` files.
- [x] Update flake8 config to exclude very large files (lemmatization tables etc.)
- [x] Update code to be compatible with flake8 rules
- [x] Fix various small bugs, inconsistencies and messy stuff in the language data
- [x] Update docs to explain new code style (`black`, `flake8`, when to use `# fmt: off` and `# fmt: on` and what `# noqa` means)
Once #2932 is merged, which auto-formats and tidies up the CLI, we'll be able to run `flake8 spacy` actually get meaningful results.
At the moment, the code style and linting isn't applied automatically, but I'm hoping that the new [GitHub Actions](https://github.com/features/actions) will let us auto-format pull requests and post comments with relevant linting information.
### Types of change
enhancement, code style
## Checklist
<!--- Before you submit the PR, go over this checklist and make sure you can
tick off all the boxes. [] -> [x] -->
- [x] I have submitted the spaCy Contributor Agreement.
- [x] I ran the tests, and all new and existing tests passed.
- [x] My changes don't require a change to the documentation, or if they do, I've added all required information.
2018-11-30 19:03:03 +03:00
|
|
|
string,
|
2019-10-01 22:36:04 +03:00
|
|
|
index_table.get(univ_pos, {}),
|
|
|
|
exc_table.get(univ_pos, {}),
|
|
|
|
rules_table.get(univ_pos, []),
|
💫 Tidy up and auto-format .py files (#2983)
<!--- Provide a general summary of your changes in the title. -->
## Description
- [x] Use [`black`](https://github.com/ambv/black) to auto-format all `.py` files.
- [x] Update flake8 config to exclude very large files (lemmatization tables etc.)
- [x] Update code to be compatible with flake8 rules
- [x] Fix various small bugs, inconsistencies and messy stuff in the language data
- [x] Update docs to explain new code style (`black`, `flake8`, when to use `# fmt: off` and `# fmt: on` and what `# noqa` means)
Once #2932 is merged, which auto-formats and tidies up the CLI, we'll be able to run `flake8 spacy` actually get meaningful results.
At the moment, the code style and linting isn't applied automatically, but I'm hoping that the new [GitHub Actions](https://github.com/features/actions) will let us auto-format pull requests and post comments with relevant linting information.
### Types of change
enhancement, code style
## Checklist
<!--- Before you submit the PR, go over this checklist and make sure you can
tick off all the boxes. [] -> [x] -->
- [x] I have submitted the spaCy Contributor Agreement.
- [x] I ran the tests, and all new and existing tests passed.
- [x] My changes don't require a change to the documentation, or if they do, I've added all required information.
2018-11-30 19:03:03 +03:00
|
|
|
)
|
2015-09-08 16:38:03 +03:00
|
|
|
return lemmas
|
2014-12-23 07:16:57 +03:00
|
|
|
|
2016-12-07 23:12:49 +03:00
|
|
|
def noun(self, string, morphology=None):
|
💫 Tidy up and auto-format .py files (#2983)
<!--- Provide a general summary of your changes in the title. -->
## Description
- [x] Use [`black`](https://github.com/ambv/black) to auto-format all `.py` files.
- [x] Update flake8 config to exclude very large files (lemmatization tables etc.)
- [x] Update code to be compatible with flake8 rules
- [x] Fix various small bugs, inconsistencies and messy stuff in the language data
- [x] Update docs to explain new code style (`black`, `flake8`, when to use `# fmt: off` and `# fmt: on` and what `# noqa` means)
Once #2932 is merged, which auto-formats and tidies up the CLI, we'll be able to run `flake8 spacy` actually get meaningful results.
At the moment, the code style and linting isn't applied automatically, but I'm hoping that the new [GitHub Actions](https://github.com/features/actions) will let us auto-format pull requests and post comments with relevant linting information.
### Types of change
enhancement, code style
## Checklist
<!--- Before you submit the PR, go over this checklist and make sure you can
tick off all the boxes. [] -> [x] -->
- [x] I have submitted the spaCy Contributor Agreement.
- [x] I ran the tests, and all new and existing tests passed.
- [x] My changes don't require a change to the documentation, or if they do, I've added all required information.
2018-11-30 19:03:03 +03:00
|
|
|
return self(string, "noun", morphology)
|
2014-12-23 07:16:57 +03:00
|
|
|
|
2016-12-07 23:12:49 +03:00
|
|
|
def verb(self, string, morphology=None):
|
💫 Tidy up and auto-format .py files (#2983)
<!--- Provide a general summary of your changes in the title. -->
## Description
- [x] Use [`black`](https://github.com/ambv/black) to auto-format all `.py` files.
- [x] Update flake8 config to exclude very large files (lemmatization tables etc.)
- [x] Update code to be compatible with flake8 rules
- [x] Fix various small bugs, inconsistencies and messy stuff in the language data
- [x] Update docs to explain new code style (`black`, `flake8`, when to use `# fmt: off` and `# fmt: on` and what `# noqa` means)
Once #2932 is merged, which auto-formats and tidies up the CLI, we'll be able to run `flake8 spacy` actually get meaningful results.
At the moment, the code style and linting isn't applied automatically, but I'm hoping that the new [GitHub Actions](https://github.com/features/actions) will let us auto-format pull requests and post comments with relevant linting information.
### Types of change
enhancement, code style
## Checklist
<!--- Before you submit the PR, go over this checklist and make sure you can
tick off all the boxes. [] -> [x] -->
- [x] I have submitted the spaCy Contributor Agreement.
- [x] I ran the tests, and all new and existing tests passed.
- [x] My changes don't require a change to the documentation, or if they do, I've added all required information.
2018-11-30 19:03:03 +03:00
|
|
|
return self(string, "verb", morphology)
|
2014-12-23 07:16:57 +03:00
|
|
|
|
2016-12-07 23:12:49 +03:00
|
|
|
def adj(self, string, morphology=None):
|
💫 Tidy up and auto-format .py files (#2983)
<!--- Provide a general summary of your changes in the title. -->
## Description
- [x] Use [`black`](https://github.com/ambv/black) to auto-format all `.py` files.
- [x] Update flake8 config to exclude very large files (lemmatization tables etc.)
- [x] Update code to be compatible with flake8 rules
- [x] Fix various small bugs, inconsistencies and messy stuff in the language data
- [x] Update docs to explain new code style (`black`, `flake8`, when to use `# fmt: off` and `# fmt: on` and what `# noqa` means)
Once #2932 is merged, which auto-formats and tidies up the CLI, we'll be able to run `flake8 spacy` actually get meaningful results.
At the moment, the code style and linting isn't applied automatically, but I'm hoping that the new [GitHub Actions](https://github.com/features/actions) will let us auto-format pull requests and post comments with relevant linting information.
### Types of change
enhancement, code style
## Checklist
<!--- Before you submit the PR, go over this checklist and make sure you can
tick off all the boxes. [] -> [x] -->
- [x] I have submitted the spaCy Contributor Agreement.
- [x] I ran the tests, and all new and existing tests passed.
- [x] My changes don't require a change to the documentation, or if they do, I've added all required information.
2018-11-30 19:03:03 +03:00
|
|
|
return self(string, "adj", morphology)
|
2016-09-27 14:52:11 +03:00
|
|
|
|
2019-10-01 22:36:04 +03:00
|
|
|
def det(self, string, morphology=None):
|
|
|
|
return self(string, "det", morphology)
|
|
|
|
|
|
|
|
def pron(self, string, morphology=None):
|
|
|
|
return self(string, "pron", morphology)
|
|
|
|
|
|
|
|
def adp(self, string, morphology=None):
|
|
|
|
return self(string, "adp", morphology)
|
|
|
|
|
|
|
|
def num(self, string, morphology=None):
|
|
|
|
return self(string, "num", morphology)
|
|
|
|
|
2016-12-07 23:12:49 +03:00
|
|
|
def punct(self, string, morphology=None):
|
💫 Tidy up and auto-format .py files (#2983)
<!--- Provide a general summary of your changes in the title. -->
## Description
- [x] Use [`black`](https://github.com/ambv/black) to auto-format all `.py` files.
- [x] Update flake8 config to exclude very large files (lemmatization tables etc.)
- [x] Update code to be compatible with flake8 rules
- [x] Fix various small bugs, inconsistencies and messy stuff in the language data
- [x] Update docs to explain new code style (`black`, `flake8`, when to use `# fmt: off` and `# fmt: on` and what `# noqa` means)
Once #2932 is merged, which auto-formats and tidies up the CLI, we'll be able to run `flake8 spacy` actually get meaningful results.
At the moment, the code style and linting isn't applied automatically, but I'm hoping that the new [GitHub Actions](https://github.com/features/actions) will let us auto-format pull requests and post comments with relevant linting information.
### Types of change
enhancement, code style
## Checklist
<!--- Before you submit the PR, go over this checklist and make sure you can
tick off all the boxes. [] -> [x] -->
- [x] I have submitted the spaCy Contributor Agreement.
- [x] I ran the tests, and all new and existing tests passed.
- [x] My changes don't require a change to the documentation, or if they do, I've added all required information.
2018-11-30 19:03:03 +03:00
|
|
|
return self(string, "punct", morphology)
|
2015-10-09 10:44:21 +03:00
|
|
|
|
2019-09-15 23:08:13 +03:00
|
|
|
def lookup(self, string, orth=None):
|
|
|
|
"""Look up a lemma in the table, if available. If no lemma is found,
|
|
|
|
the original string is returned.
|
|
|
|
|
|
|
|
string (unicode): The original string.
|
|
|
|
orth (int): Optional hash of the string to look up. If not set, the
|
|
|
|
string will be used and hashed.
|
|
|
|
RETURNS (unicode): The lemma if the string was found, otherwise the
|
|
|
|
original string.
|
|
|
|
"""
|
2019-10-01 22:36:04 +03:00
|
|
|
lookup_table = self.lookups.get_table("lemma_lookup", {})
|
2019-09-15 23:08:13 +03:00
|
|
|
key = orth if orth is not None else string
|
2019-10-01 22:36:04 +03:00
|
|
|
if key in lookup_table:
|
|
|
|
return lookup_table[key]
|
2017-10-11 14:25:51 +03:00
|
|
|
return string
|
|
|
|
|
2019-10-01 22:36:04 +03:00
|
|
|
def lemmatize(self, string, index, exceptions, rules):
|
|
|
|
orig = string
|
|
|
|
string = string.lower()
|
|
|
|
forms = []
|
|
|
|
oov_forms = []
|
|
|
|
for old, new in rules:
|
|
|
|
if string.endswith(old):
|
|
|
|
form = string[: len(string) - len(old)] + new
|
|
|
|
if not form:
|
|
|
|
pass
|
|
|
|
elif form in index or not form.isalpha():
|
|
|
|
forms.append(form)
|
|
|
|
else:
|
|
|
|
oov_forms.append(form)
|
|
|
|
# Remove duplicates but preserve the ordering of applied "rules"
|
|
|
|
forms = list(OrderedDict.fromkeys(forms))
|
|
|
|
# Put exceptions at the front of the list, so they get priority.
|
|
|
|
# This is a dodgy heuristic -- but it's the best we can do until we get
|
|
|
|
# frequencies on this. We can at least prune out problematic exceptions,
|
|
|
|
# if they shadow more frequent analyses.
|
|
|
|
for form in exceptions.get(string, []):
|
|
|
|
if form not in forms:
|
|
|
|
forms.insert(0, form)
|
|
|
|
if not forms:
|
|
|
|
forms.extend(oov_forms)
|
|
|
|
if not forms:
|
|
|
|
forms.append(orig)
|
|
|
|
return forms
|