In this article, we will focus on tasks to evaluate inputs, which are important for ensuring the quality and safety of the system. For tasks that require multiple sets of instructions to handle different cases, it can be beneficial to first classify the type of query and then use that classification to determine which instructions to use. This can be achieved by defining fixed categories and hard-coding instructions that are relevant for handling tasks in a given category. For example, when building a customer service assistant, it might be important to first classify the type of query and then determine which instructions to use based on that classification. Let’s consider an example to make this clearer. Suppose we have a system message that instructs the model to classify customer service queries into primary and secondary categories and provide the output in a JSON format. The primary categories can be billing, technical support, account management, or general inquiry. The secondary categories can be unsubscribe, upgrade, and so on.