Bonjour @didmar!
Thanks for your question! I think you're asking why the active learning recipe frames tasks as binary, not like a manual recipe like ner.correct
. This has come up before:
As Matt mentioned, this is just a design choice to avoid cramming too many things within the built-in recipes.
There is nothing stopping you from developing your own custom recipe to do this. It's important to think of the built-in recipes as the floor of what's possible, not the ceiling of what's possible. The built-in recipes are there to get you started with smart defaults, but may need to be modified or extended.
One Prodigy pro tip: You can view the built-in recipes by finding your installed Prodigy package location (run prodigy stats
and view Location:
), and then find the recipes
folder. For example, the ner
recipes can be found inrecipes/ner.py
. If you want, you can combine and modify the recipes to your preferences by using different sorters. We outline in the NER docs pseudo code to write a custom recipe with NER active learning.
Somewhat related, Matt mentioned in this post earlier some of the evolution in Prodigy's custom recipes design and we're we've had to rethink over time:
Thank you for this feedback! I'm going to write up an internal ticket exploring more. If you have other feedback, please fill out our user survey. It's given us a treasure-trove of fixes and enhancements on top of our upcoming releases.