Click the arrow in the box shown below and you will be presented with a dropdown menu of all of the entities that you are able to enable for that dataset. Simply click all of the entities you want to enable before creating the dataset. If you add any in error, you can click the ‘X’ icon next to the entity name to remove it.
To understand more about how to create a new dataset, see here.
Create new dataset modal
Enabling, updating, and disabling entities on an existing dataset
The above sections have covered how to enable and update existing pre-trained entities for both new and existing datasets. In each instance, for either a new or existing dataset, you can also create new entities.
Newly created entities can be based on an existing pre-trained entity or can be trained from scratch (like a new label).
You can do this by clicking the '+' icon in the entity box, either in the 'Create dataset' flow or in the dataset settings page (as shown above).
This will bring up the 'Add a new entity' modal as shown below.
Here you can set the entity base, title, and API name, as well as selecting whether the entity is trainable or not (these can be updated later as shown above).
When you've filled in each of the fields (explained below), simply click 'Create'.
Create new entity modal
- This will serve as the initial state for your new entity, and the dropdown will contain a list of all the pre-trained entities available to you in Re:infer
- For example, if you select 'Date' as your base entity, all of the entities predicted for this kind will be dates, and you could then train Re:infer to only recognise specific dates
- If you want to train an entity entirely from scratch, you can select 'None - Train from scratch', and then you essentially start with a blank canvas when training the entity. Re:infer's predictions for this entity will be entirely based on the training examples you provide
- The entity title is the name of the entity that will appear in the UI of the platform
- The API name of the entity is what will be returned via the API when it provides predictions for verbatims
- The API name cannot contain any spaces or punctuation except for dash ( - ) and underscore ( _ )