# A recipe to correct NER labels from annotated offsets rather than suggested by a spaCy model

**URL:** <https://support.prodi.gy/t/a-recipe-to-correct-ner-labels-from-annotated-offsets-rather-than-suggested-by-a-spacy-model/2485>\
**Category:** Uncategorized\
**Tags:** usage, ner, solved\
**Created:** [January 30, 2020, 3:11pm UTC](https://support.prodi.gy/t/a-recipe-to-correct-ner-labels-from-annotated-offsets-rather-than-suggested-by-a-spacy-model/2485 "2020-01-30T15:11:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andrey](https://avatars.discourse-cdn.com/v4/letter/a/73ab20/32.png) [@Andrey](https://support.prodi.gy/u/Andrey)\
**Post date:** [January 30, 2020, 3:11pm UTC](https://support.prodi.gy/t/a-recipe-to-correct-ner-labels-from-annotated-offsets-rather-than-suggested-by-a-spacy-model/2485/1 "2020-01-30T15:11:19Z")

</div>

I am sure I've seen it somewhere, but can't figure it now. Is there a simple way to review and amend annotated (NER) examples using offset annotations?

For example:

Instead of the collected wrong annotation:

{"text": 'A cat drives Porsche', "spans": [{'start':2, 'end': 5, 'label':'ANIMAL'}, {'start':13, 'end': 20, 'label':'ANIMAL'}]

I can upload it to Prodigy and correct the label of the last entity and save:

{"text": 'A cat drives Porsche', "spans": [{'start':2, 'end': 5, 'label':'ANIMAL'}, {'start':13, 'end': 20, 'label':'CAR'}]

Thanks!

P.S. I tried `review` recipe with `--view-id` option, but I was not able to make any changes.

---

<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:** [January 31, 2020, 11:20am UTC](https://support.prodi.gy/t/a-recipe-to-correct-ner-labels-from-annotated-offsets-rather-than-suggested-by-a-spacy-model/2485/2 "2020-01-31T11:20:56Z")

</div>

Hi! I think the easiest solution would be to load your data into `ner.manual`. The recipe respects pre-defined entities and will take care of mapping them to tokens. You'll then be able to see the prehighlighted spans, and correct them if needed.

> [@Andrey](#):
>
> P.S. I tried `review` recipe with `--view-id` option, but I was not able to make any changes.

If you have multiple conflicting annotations on the same data, the `review` recipe is a nice way to reconcile them and create one final "master annotation". However, if you want the spans to be editable, you'll need to load in datasets with the `ner_manual` view ID and make sure it's pre-tokenized. If you're just using the `ner` interface, the spans won't be editable and all you get to annotate is the accept/reject decision.