# Error while using ner.match for pattern matching

**URL:** <https://support.prodi.gy/t/error-while-using-ner-match-for-pattern-matching/874>\
**Category:** Uncategorized\
**Tags:** usage, ner, solved\
**Created:** [October 12, 2018, 12:51am UTC](https://support.prodi.gy/t/error-while-using-ner-match-for-pattern-matching/874 "2018-10-12T00:51:19Z")\
**Posts on this page:** 1\
**Showing post:** 9

<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:** [October 13, 2018, 10:37am UTC](https://support.prodi.gy/t/error-while-using-ner-match-for-pattern-matching/874/9 "2018-10-13T10:37:20Z")

</div>

Glad it'S working! Moving to the next thread, answer see here:

> [@ner.match to jsonl without getting into the interface](https://support.prodi.gy/t/ner-match-to-jsonl-without-getting-into-the-interface/879/2):
>
> The main idea of ner.match is to give you an interface so you or your annotators can accept and reject matches to bootstrap training sets with positive and negative examples, and to allow creating training data from patterns that produce false positives and to explore patterns interactively. If you only want to create matches based on patterns, you could just use spaCy's Matcher directly and save the matches as JSONL? If you do want to annotate with Prodigy but with custom match logic (or any o…

---

_[View the full topic](https://support.prodi.gy/t/error-while-using-ner-match-for-pattern-matching/874)._