3 ms·
The severity needing to be at the end was an important insight. It made the results much better but not quite good enough. We had it output a json with fields
by dakshgupta 2y ago
The severity needing to be at the end was an important insight. It made the results much better but not quite good enough.
We had it output a json with fields {comment: string, severity: string} in that order.
- Merik 2y agoAnother variation on this is to think about tokens and definitions. Numbers don’t have inherent meaning for your use case, so if you use numbers you need to provide an explicit definition of each rating number in the prompt. Similarly, and more effectively is to use labels such as low-quality, medium-quality, high-quality, and again providing an explicit definition of the label; one step further is to use explicit self describing label (along with detailed definition) such as “trivial-observation-on-naming-convention” or “insightful-identification-on-missed-corner-case”. Effectively you are turning a somewhat arbitrary numeric “rating” task , into a multi label classification problem with well defined labels. The natural evolution is to then train a BERT based classifier or similar on the set of labels and comments, which will get you a model judge that is super fast and can achieve good accuracy.