💫 Update website (#3285)
<!--- Provide a general summary of your changes in the title. -->
## Description
The new website is implemented using [Gatsby](https://www.gatsbyjs.org) with [Remark](https://github.com/remarkjs/remark) and [MDX](https://mdxjs.com/). This allows authoring content in **straightforward Markdown** without the usual limitations. Standard elements can be overwritten with powerful [React](http://reactjs.org/) components and wherever Markdown syntax isn't enough, JSX components can be used. Hopefully, this update will also make it much easier to contribute to the docs. Once this PR is merged, I'll implement auto-deployment via [Netlify](https://netlify.com) on a specific branch (to avoid building the website on every PR). There's a bunch of other cool stuff that the new setup will allow us to do – including writing front-end tests, service workers, offline support, implementing a search and so on.
This PR also includes various new docs pages and content.
Resolves #3270. Resolves #3222. Resolves #2947. Resolves #2837.
### Types of change
enhancement
## 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.
2019-02-17 18:31:19 +00:00
|
|
|
---
|
|
|
|
title: Lemmatizer
|
|
|
|
teaser: Assign the base forms of words
|
|
|
|
tag: class
|
|
|
|
source: spacy/lemmatizer.py
|
|
|
|
---
|
|
|
|
|
|
|
|
The `Lemmatizer` supports simple part-of-speech-sensitive suffix rules and
|
|
|
|
lookup tables.
|
|
|
|
|
|
|
|
## Lemmatizer.\_\_init\_\_ {#init tag="method"}
|
|
|
|
|
|
|
|
Create a `Lemmatizer`.
|
|
|
|
|
|
|
|
> #### Example
|
|
|
|
>
|
|
|
|
> ```python
|
|
|
|
> from spacy.lemmatizer import Lemmatizer
|
|
|
|
> lemmatizer = Lemmatizer()
|
|
|
|
> ```
|
|
|
|
|
|
|
|
| Name | Type | Description |
|
|
|
|
| ------------ | ------------- | ---------------------------------------------------------- |
|
|
|
|
| `index` | dict / `None` | Inventory of lemmas in the language. |
|
|
|
|
| `exceptions` | dict / `None` | Mapping of string forms to lemmas that bypass the `rules`. |
|
|
|
|
| `rules` | dict / `None` | List of suffix rewrite rules. |
|
|
|
|
| `lookup` | dict / `None` | Lookup table mapping string to their lemmas. |
|
|
|
|
| **RETURNS** | `Lemmatizer` | The newly created object. |
|
|
|
|
|
|
|
|
## Lemmatizer.\_\_call\_\_ {#call tag="method"}
|
|
|
|
|
|
|
|
Lemmatize a string.
|
|
|
|
|
|
|
|
> #### Example
|
|
|
|
>
|
|
|
|
> ```python
|
|
|
|
> from spacy.lemmatizer import Lemmatizer
|
2019-09-12 14:26:33 +00:00
|
|
|
> rules = {"noun": [["s", ""]]}
|
|
|
|
> lemmatizer = Lemmatizer(index={}, exceptions={}, rules=rules)
|
2019-09-12 14:11:15 +00:00
|
|
|
> lemmas = lemmatizer("ducks", "NOUN")
|
|
|
|
> assert lemmas == ["duck"]
|
💫 Update website (#3285)
<!--- Provide a general summary of your changes in the title. -->
## Description
The new website is implemented using [Gatsby](https://www.gatsbyjs.org) with [Remark](https://github.com/remarkjs/remark) and [MDX](https://mdxjs.com/). This allows authoring content in **straightforward Markdown** without the usual limitations. Standard elements can be overwritten with powerful [React](http://reactjs.org/) components and wherever Markdown syntax isn't enough, JSX components can be used. Hopefully, this update will also make it much easier to contribute to the docs. Once this PR is merged, I'll implement auto-deployment via [Netlify](https://netlify.com) on a specific branch (to avoid building the website on every PR). There's a bunch of other cool stuff that the new setup will allow us to do – including writing front-end tests, service workers, offline support, implementing a search and so on.
This PR also includes various new docs pages and content.
Resolves #3270. Resolves #3222. Resolves #2947. Resolves #2837.
### Types of change
enhancement
## 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.
2019-02-17 18:31:19 +00:00
|
|
|
> ```
|
|
|
|
|
|
|
|
| Name | Type | Description |
|
|
|
|
| ------------ | ------------- | -------------------------------------------------------------------------------------------------------- |
|
|
|
|
| `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 / `None` | Morphological features following the [Universal Dependencies](http://universaldependencies.org/) scheme. |
|
|
|
|
| **RETURNS** | list | The available lemmas for the string. |
|
|
|
|
|
|
|
|
## Lemmatizer.lookup {#lookup tag="method" new="2"}
|
|
|
|
|
|
|
|
Look up a lemma in the lookup table, if available. If no lemma is found, the
|
|
|
|
original string is returned. Languages can provide a
|
|
|
|
[lookup table](/usage/adding-languages#lemmatizer) via the `lemma_lookup`
|
|
|
|
variable, set on the individual `Language` class.
|
|
|
|
|
|
|
|
> #### Example
|
|
|
|
>
|
|
|
|
> ```python
|
2019-09-12 14:11:15 +00:00
|
|
|
> lookup = {"going": "go"}
|
💫 Update website (#3285)
<!--- Provide a general summary of your changes in the title. -->
## Description
The new website is implemented using [Gatsby](https://www.gatsbyjs.org) with [Remark](https://github.com/remarkjs/remark) and [MDX](https://mdxjs.com/). This allows authoring content in **straightforward Markdown** without the usual limitations. Standard elements can be overwritten with powerful [React](http://reactjs.org/) components and wherever Markdown syntax isn't enough, JSX components can be used. Hopefully, this update will also make it much easier to contribute to the docs. Once this PR is merged, I'll implement auto-deployment via [Netlify](https://netlify.com) on a specific branch (to avoid building the website on every PR). There's a bunch of other cool stuff that the new setup will allow us to do – including writing front-end tests, service workers, offline support, implementing a search and so on.
This PR also includes various new docs pages and content.
Resolves #3270. Resolves #3222. Resolves #2947. Resolves #2837.
### Types of change
enhancement
## 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.
2019-02-17 18:31:19 +00:00
|
|
|
> lemmatizer = Lemmatizer(lookup=lookup)
|
2019-09-12 14:11:15 +00:00
|
|
|
> assert lemmatizer.lookup("going") == "go"
|
💫 Update website (#3285)
<!--- Provide a general summary of your changes in the title. -->
## Description
The new website is implemented using [Gatsby](https://www.gatsbyjs.org) with [Remark](https://github.com/remarkjs/remark) and [MDX](https://mdxjs.com/). This allows authoring content in **straightforward Markdown** without the usual limitations. Standard elements can be overwritten with powerful [React](http://reactjs.org/) components and wherever Markdown syntax isn't enough, JSX components can be used. Hopefully, this update will also make it much easier to contribute to the docs. Once this PR is merged, I'll implement auto-deployment via [Netlify](https://netlify.com) on a specific branch (to avoid building the website on every PR). There's a bunch of other cool stuff that the new setup will allow us to do – including writing front-end tests, service workers, offline support, implementing a search and so on.
This PR also includes various new docs pages and content.
Resolves #3270. Resolves #3222. Resolves #2947. Resolves #2837.
### Types of change
enhancement
## 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.
2019-02-17 18:31:19 +00:00
|
|
|
> ```
|
|
|
|
|
|
|
|
| Name | Type | Description |
|
|
|
|
| ----------- | ------- | ----------------------------------------------------------------- |
|
|
|
|
| `string` | unicode | The string to look up. |
|
|
|
|
| **RETURNS** | unicode | The lemma if the string was found, otherwise the original string. |
|
|
|
|
|
|
|
|
## Lemmatizer.is_base_form {#is_base_form tag="method"}
|
|
|
|
|
|
|
|
Check whether we're dealing with an uninflected paradigm, so we can avoid
|
|
|
|
lemmatization entirely.
|
|
|
|
|
|
|
|
> #### Example
|
|
|
|
>
|
|
|
|
> ```python
|
|
|
|
> pos = "verb"
|
|
|
|
> morph = {"VerbForm": "inf"}
|
|
|
|
> is_base_form = lemmatizer.is_base_form(pos, morph)
|
|
|
|
> assert is_base_form == True
|
|
|
|
> ```
|
|
|
|
|
|
|
|
| Name | Type | Description |
|
|
|
|
| ------------ | ------------- | --------------------------------------------------------------------------------------- |
|
|
|
|
| `univ_pos` | unicode / int | The token's universal part-of-speech tag. |
|
|
|
|
| `morphology` | dict | The token's morphological features. |
|
|
|
|
| **RETURNS** | bool | Whether the token's part-of-speech tag and morphological features describe a base form. |
|
|
|
|
|
|
|
|
## Attributes {#attributes}
|
|
|
|
|
|
|
|
| Name | Type | Description |
|
|
|
|
| ----------------------------------------- | ------------- | ---------------------------------------------------------- |
|
|
|
|
| `index` | dict / `None` | Inventory of lemmas in the language. |
|
|
|
|
| `exc` | dict / `None` | Mapping of string forms to lemmas that bypass the `rules`. |
|
|
|
|
| `rules` | dict / `None` | List of suffix rewrite rules. |
|
|
|
|
| `lookup_table` <Tag variant="new">2</Tag> | dict / `None` | The lemma lookup table, if available. |
|