explosion/spaCy
1
1
Fork 0
mirror of https://github.com/explosion/spaCy.git synced 2024-12-25 17:36:30 +03:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1720 from mpuels/patch-6

Browse Source 
doc: Fix minor mistakes
This commit is contained in:
Ines Montani 2017-12-13 11:11:59 +00:00 committed by GitHub
commit 7a6f24a194
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
website/usage/_training/_tagger-parser.jade
View File

@ -95,11 +95,11 @@ p
+h(3, "intent-parser") Training a parser for custom semantics
p
| spaCy's parser component can be used to trained to predict any type
| spaCy's parser component can be used to be trained to predict any type
| of tree structure over your input text – including
| #[strong semantic relations] that are not syntactic dependencies. This
| can be useful to for #[strong conversational applications], which need to
| predict trees over whole documents or chat logs, with connections between
| predict trees over whole documents or chat logs, with connections between
| the sentence roots used to annotate discourse structure. For example, you
| can train spaCy's parser to label intents and their targets, like
| attributes, quality, time and locations. The result could look like this:
@ -132,7 +132,7 @@ p
| to do this automatically – just make sure to add it #[code before='parser'].
p
| The following example example shows a full implementation of a training
| The following example shows a full implementation of a training
| loop for a custom message parser for a common "chat intent": finding
| local businesses. Our message semantics will have the following types
| of relations: #[code ROOT], #[code PLACE], #[code QUALITY],