# Best labeling strategy for hierarchical concepts

**URL:** <https://support.prodi.gy/t/best-labeling-strategy-for-hierarchical-concepts/1262>\
**Category:** Uncategorized\
**Tags:** usage, textcat\
**Created:** [March 1, 2019, 3:48pm UTC](https://support.prodi.gy/t/best-labeling-strategy-for-hierarchical-concepts/1262 "2019-03-01T15:48:26Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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:** [March 1, 2019, 6:12pm UTC](https://support.prodi.gy/t/best-labeling-strategy-for-hierarchical-concepts/1262/3 "2019-03-01T18:12:36Z")

</div>

There was a similar question the other day and I wrote up some ideas for a workflow that starts with the top-level categories and moves on to the sub categories, using a custom recipe that creates multiple choice tasks automatically:

> [@Does Prodigy supports hierarchical annotation?](https://support.prodi.gy/t/does-prodigy-supports-hierarchical-annotation/1249/2):
>
> Prodigy itself is pretty agnostic to what your annotations “mean” so you can definitely build a workflow like this. The only thing that’s kinda built-in is a strong focus on single decisions at a time and automating as much as possible. One approach could be to use the [choice interface](https://prodi.gy/demo?view_id=textchoice) and start by annotating the top-level buckets like A, B and C, without worrying about the lower-level categories. [See here](https://prodi.gy/docs/workflow-custom-recipes#example-choice) for an example recipe code. In the next step, you can then stream in the examples again a…

But as Justin mentioned, you might find that structuring it as a binary task is actually much better and faster, especially for the top-level decisions.

---

_[View the full topic](https://support.prodi.gy/t/best-labeling-strategy-for-hierarchical-concepts/1262)._