# Understanding ner.batch-train stats

**URL:** <https://support.prodi.gy/t/understanding-ner-batch-train-stats/412>\
**Category:** Uncategorized\
**Tags:** usage, ner, solved, best-practices\
**Created:** [March 19, 2018, 10:53am UTC](https://support.prodi.gy/t/understanding-ner-batch-train-stats/412 "2018-03-19T10:53:54Z")\
**Posts on this page:** 1\
**Showing post:** 8

<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 26, 2018, 3:01pm UTC](https://support.prodi.gy/t/understanding-ner-batch-train-stats/412/8 "2018-10-26T15:01:46Z")

</div>

> [@Mindaugas](#):
>
> Does this mean that, while training, the model will assume that entities are the ones marked and the rest is not an entity?

If you run `ner.batch` train with the `--no-missing` flag, then yes. All tokens that are not part of an entity will be assumed to be not part of an entity. Otherwise, non-marked tokens will be treated as missing values.

> [@Mindaugas](#):
>
> Are there use cases when someone would like to mark something in ner.manual and reject?

The recipe / interface lets you assign labels to text – what they mean is up to you. So you could use the "reject" action to create negative examples, or to mark examples with fundamental problems, like wrong tokenization. Also see this thread:

> [@When to reject in ner.manual or ner.make-gold?](https://support.prodi.gy/t/when-to-reject-in-ner-manual-or-ner-make-gold/892/2):
>
> I think I found the answer while looking for something else. In this answer @honnibal brings it right to the point: To save others the click: One should only accept. Rejection is a way to mark serious trouble like wrong tokenizations.

---

_[View the full topic](https://support.prodi.gy/t/understanding-ner-batch-train-stats/412)._