# Training dependency parser

**URL:** <https://support.prodi.gy/t/training-dependency-parser/375>\
**Category:** Uncategorized\
**Tags:** usage, ner, done, spacy\
**Created:** [March 7, 2018, 2:09pm UTC](https://support.prodi.gy/t/training-dependency-parser/375 "2018-03-07T14:09:54Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\
**Post date:** [March 7, 2018, 4:55pm UTC](https://support.prodi.gy/t/training-dependency-parser/375/5 "2018-03-07T16:55:02Z")

</div>

For the annotation part, see my comment on this thread:

> [@Recipe for custom intent parser to train spaCy](https://support.prodi.gy/t/recipe-for-custom-intent-parser-to-train-spacy/374/2):
>
> Hi! So I guess you’re referring to the spaCy example of training an intent parser using spaCy’s dependency parser, right? [https://github.com/explosion/spaCy/blob/master/examples/training/train\_intent\_parser.py](https://github.com/explosion/spaCy/blob/master/examples/training/train_intent_parser.py) The good news is, we’re currently working on getting Prodigy v1.4.0 ready (coming this week!), which will include an experimental built-in interface for dependency annotation, as well as dep.teach and dep.batch-train recipes. Those will work with any spaCy model – so you can use it to im…

---

_[View the full topic](https://support.prodi.gy/t/training-dependency-parser/375)._