# 80 Entities ner.manual **URL:** \ **Category:** Uncategorized\ **Tags:** usage, ner, solved\ **Created:** [August 11, 2021, 12:39pm UTC](https://support.prodi.gy/t/80-entities-ner-manual/4552 "2021-08-11T12:39:17Z")\ **Posts on this page:** 1\ **Showing post:** 3
**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:** [August 12, 2021, 12:23am UTC](https://support.prodi.gy/t/80-entities-ner-manual/4552/3 "2021-08-12T00:23:22Z")
Yeah, I agree, if your goal is to annotate named entities or similar spans and you ended up with this many labels, we'd typically recommend rethinking your label scheme and structuring your task differently. You're making your life a lot harder this way, and it'll be much more difficult to create consistently annotated data with enough coverage, and your model will be much less likely to learn from it effectively. Also see this thread for more background and suggestions: > [@NER with dozens of entities](https://support.prodi.gy/t/ner-with-dozens-of-entities/4139/3): > > As a more general comment/question: Is your goal to actually train an NER model? If so, are you sure you want to structure your annotation task and model this way and have that many labels? You might be making your life a lot harder this way, because you'll need significantly more data and make sure you have enough examples per label so the model can distinguish between them. If the labels are hierarchical, you'd also be encoding multiple aspects within each annotation that the model has to lear… --- _[View the full topic](https://support.prodi.gy/t/80-entities-ner-manual/4552)._