Rooba
/
spaCy
mirror of https://github.com/explosion/spaCy.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Auto-format

This commit is contained in:
Ines Montani 2019-08-06 12:13:31 +02:00
parent 15be09ceb0
commit 2bfae0b167
1 changed files with 15 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
website/docs/usage/rule-based-matching.md
View File

@ -158,7 +158,7 @@ The available token pattern keys are uppercase versions of the
rule-based matching are: rule-based matching are:
| Attribute | Type |  Description | | Attribute | Type |  Description |
| -------------------------------------- | ------- | ------------------------------------------------------------------------------------------------ | | -------------------------------------- | ------- | ------------------------------------------------------------------------------------------------------ |
| `ORTH` | unicode | The exact verbatim text of a token. | | `ORTH` | unicode | The exact verbatim text of a token. |
| `TEXT` <Tag variant="new">2.1</Tag> | unicode | The exact verbatim text of a token. | | `TEXT` <Tag variant="new">2.1</Tag> | unicode | The exact verbatim text of a token. |
| `LOWER` | unicode | The lowercase form of the token text. | | `LOWER` | unicode | The lowercase form of the token text. |
@ -1140,8 +1140,9 @@ To apply this logic automatically when we process a text, we can add it to the
above logic also expects that entities are merged into single tokens. spaCy above logic also expects that entities are merged into single tokens. spaCy
ships with a handy built-in `merge_entities` that takes care of that. Instead of ships with a handy built-in `merge_entities` that takes care of that. Instead of
just printing the result, you could also write it to just printing the result, you could also write it to
[custom attributes](/usage/processing-pipelines#custom-components-attributes) on the [custom attributes](/usage/processing-pipelines#custom-components-attributes) on
entity `Span` – for example `._.orgs` or `._.prev_orgs` and `._.current_orgs`. the entity `Span` – for example `._.orgs` or `._.prev_orgs` and
`._.current_orgs`.
> #### Merging entities > #### Merging entities
> >