# make gold multilabel

**URL:** <https://support.prodi.gy/t/make-gold-multilabel/2148>\
**Category:** Uncategorized\
**Tags:** usage, textcat\
**Created:** [October 26, 2019, 5:10pm UTC](https://support.prodi.gy/t/make-gold-multilabel/2148 "2019-10-26T17:10:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dany](https://avatars.discourse-cdn.com/v4/letter/d/5e9695/32.png) [@Dany](https://support.prodi.gy/u/Dany)\
**Post date:** [October 26, 2019, 5:10pm UTC](https://support.prodi.gy/t/make-gold-multilabel/2148/1 "2019-10-26T17:10:51Z")

</div>

Hi there,

I am trying to reduce an existing labelling scheme to 20 labels, and I suspect that this could give me a warm start but that there will also be a lot of errors. My planned workflow is:

- try my best to distil the existing labelled categories into the 20 I've determined to be independent
- train a model on this dataset to get an idea of initial performance; which labels perform worst, etc.
- correct incorrect labels using the trained model (or a blank model?) and `manual` or `make-gold`.

I am a unsure of the best workflow generally, but also whether I can just use my custom manual recipe to correct/ extend the dataset, or whether I should try and customize the `make gold` recipe for a multilabel task?

---

<div class="post-metadata">

**Author:** ![honnibal](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/honnibal/32/35_2.png) [@honnibal](https://support.prodi.gy/u/honnibal)\
**Post date:** [November 1, 2019, 4:20pm UTC](https://support.prodi.gy/t/make-gold-multilabel/2148/2 "2019-11-01T16:20:54Z")

</div>

Hi @dany,

I think I might be understanding your problem incorrectly. Do you already have data annotated with some higher number of labels --- say, 100 entity types --- and you want to reduce that to only 20 entity types?

Is there a many-to-one mapping of your fine-grained types to the course-grained ones? So for instance, if you have labels for `CAR` and `LAPTOP`, can you map both of those to `PRODUCT`? Or are there categories where the mapping is more complicated: for instance, maybe your fine-grained labels have a category `MUSICIAN`, some of which you'd sort into `PERSON` and some of which you'd sort into `ORG`?

If you have a many-to-one mapping, obviously that's pretty easy. But even for the many-to-many cases, I would suggest making a frequency list of your entities, and working down the types, rather than the tokens. For instance, you might have several mentions of an entity like `Justin Bieber`. You're going to re-type all of those instances to the same category, so there's no need to do them all individually --- doing them individually can only introduce errors, because it's hard to remember all the decisions you made.