text
stringlengths 8.98k
10.9k
|
|---|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the venue information document in the prompt is relevant for answering the user query. Ensure you take proper care and consideration to ensure you do not make the wrong decision.
To ensure you are able to make the correct decision, here is a breakdown of what is covered in the venue information document:
VENUE INFORMATION DOCUMENT CONTENTS:
- An abstract/blurb describing the venue.
- Information on location and accessability.
- Information on parking at the venue.
- Interior design and ambiance.
- The seating layout and capacity of the venue.
- The facilities and ammenities available at the venue(eg. wifi, ventillation system, sound system, projectors, restrooms facilites).
- All Information that is related to the physial space wil be in this document - this includes the dining area, bar, theatre, restrooms etc.
- Contact information for additional more complex queries.
- Service charges & all other additional charges.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Dress code.
- Minimum age restrictions.
- Minimum spend policy.
- Rules around patrons using their own decorations on reserved areas.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query is in one of the listed crossover topics, you exclude the document. The reasoning will be explained in the prompt.
The food and drink policy within the venue information document ONLY COVERS the rules and policies around bring in outside food and drinks. And storing unfinished alcohol. All food and drink policy outside of this can be considered crossover topics and will be handled in the menu document.
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude.
The venue information document does NOT have any information about the opening times of the venue. Queries about opening hours are thus a crossover topic and will be handled in the opening hours document.
ALL QUERIES THAT MENTION ANY PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE SHOULD INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT. EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in json format.
Ensure you follow the following json schema no matter the document or query you are working with:
EXAMPLE JSON OUTPUT:
{{
"reasoning": "This is where you explain your reasoning for the decision you made.",
"decision": "Will be either "include" or "exclude"."
}}
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
can i takea any unfinished alcohol home if I cant finish?
### TASK ###
You are responsible for making a decision on whether the venue information document is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
### CROSSOVER TOPICS THAT ARE NOT IN THE VENUE INFORMATION DOCUMENT ###
ALL QUERIES HANDLED BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE VENUE INFORMATION DOCUMENT FROM THE CONTEXT.
If these arise note that the menu doc would NOT be needed as the answer will lie elsewhere, outside of your scope;
RESERVATIONS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
Information on the reservation policies of the venue, this includes;
- Walk in customers seating policy.
- Minimum spends for reserved areas.
- Time limits on reservations.
- Cancellation policys (regarding late arrivals or no shows).
- How groups and large booking are handled.
Other detailed information includes;
- Detailed information on the seating layouts and descriptive information about the different parts of the venue which can be used to compare against the customers requested group size.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
UPCOMING EVENTS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information on the date, time, whether a ticket is needed, and a brief description of the event. Also rules and policies surrounding the specific events.
Any Information asking about upcoming events planned by the business should be referred onto the upcoming events document and thus exclude the venue information document.
MENU DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Pricing ,Ingredients and descriptions of all menu items.(It goes without saying availibility of menu items is not in the venue information document).
- This covers all food, drink and shisha related queries.
- Delivery availability of products, including services like Uber Eats or Foodpanda.
- Takeway of menu items policy.
- Customization of menu items.
- Special offers or happy hours.
- Last orders time for all menu items.
OPENING HOURS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- The 7 day regular working schedule of the venue. Is covered in the opening hours document.
- Last orders time and subsequent closing time for the kitchen, bar etc. Are covered in the opening hours document. Not the venue information document.
Any query that is answered by the opening hours document should not include the venue information document as it would be irrelevant context.
ALL OF THE QUERIES WHICH ARE DIRECTLY ANSWERABLE BY THE CORSSOVER TOPICS SHOULD NOT INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT.
### GUIDELINES ###
If a query asks about a "dining hall", a "theatre" or "bar" or anything that relates to a physical space. We will need the venue information to check if the venue has that space or not. We are not just including conntext to directly answer the querybut also to fact-check if the assumptions made in the query were correct.
Furthermore if the query mentions restrooms, or other facilities that are part of the physical space, the venue informationdocument should be included in the context regardless of the crux of the query.
EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY, IF IT MENTIONS A PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE, THE VENUE INFORMATION DOCUMENT SHOULD BE INCLUDED IN THE CONTEXT.
If a customer mentions wanting to do some form of activity at the venue, like reading a book, studying, working, or having a meeting. The venue information document should be included in the context. As the next node will need to know if the venue has the space to accomodate the customer's request but more importantly it give context on the interior style and ambiance and whether said activity is suitiable.
For example if a customer asks whether its possible to book a private event, the venue information is needed to provide a full a comprehensive answer. As if included, the next node will now be able to provide information on the venues spaces, ammenities and other parts of the physical space that would make it suitiable or not for a private event or custom booking.
The worst case scenario is a customer arrives for a booking but the venue cannot accomodate them due to a policy or physical constraint that was not considered in the response.
<｜Assistant｜>
<think>
Okay, let's tackle this query. The user is asking if they can take any unfinished alcohol home if they can't finish it.
First, I need to check what the venue information document covers. From the guidelines, the venue document includes policies on storing unfinished alcohol. The user's question is directly about this policy, which is listed under the venue document contents.
Next, I should verify if this falls under any crossover topics. The menu document handles food and drink items but not the policies about bringing or storing them. The other documents like reservations, events, or opening hours don't cover this either.
Also, the query doesn't mention any physical spaces, but since the policy is explicitly part of the venue information, it's definitely included there. There's no overlap with other documents here.
Therefore, the venue information document is relevant and should be included to answer the user's question accurately.
</think>
{
"reasoning": "The query asks about the policy regarding taking unfinished alcohol home, which is explicitly covered under the venue information document's section on rules around storing unfinished alcohol. This topic is within the scope of the venue information document and does not fall under any of the crossover topics handled by other documents like reservations, menu, upcoming events, or opening hours. Therefore, the venue information document is relevant and necessary to provide an accurate answer.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the venue information document in the prompt is relevant for answering the user query. Ensure you take proper care and consideration to ensure you do not make the wrong decision.
To ensure you are able to make the correct decision, here is a breakdown of what is covered in the venue information document:
VENUE INFORMATION DOCUMENT CONTENTS:
- An abstract/blurb describing the venue.
- Information on location and accessability.
- Information on parking at the venue.
- Interior design and ambiance.
- The seating layout and capacity of the venue.
- The facilities and ammenities available at the venue(eg. wifi, ventillation system, sound system, projectors, restrooms facilites).
- All Information that is related to the physial space wil be in this document - this includes the dining area, bar, theatre, restrooms etc.
- Contact information for additional more complex queries.
- Service charges & all other additional charges.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Dress code.
- Minimum age restrictions.
- Minimum spend policy.
- Rules around patrons using their own decorations on reserved areas.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query is in one of the listed crossover topics, you exclude the document. The reasoning will be explained in the prompt.
The food and drink policy within the venue information document ONLY COVERS the rules and policies around bring in outside food and drinks. And storing unfinished alcohol. All food and drink policy outside of this can be considered crossover topics and will be handled in the menu document.
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude.
The venue information document does NOT have any information about the opening times of the venue. Queries about opening hours are thus a crossover topic and will be handled in the opening hours document.
ALL QUERIES THAT MENTION ANY PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE SHOULD INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT. EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in json format.
Ensure you follow the following json schema no matter the document or query you are working with:
EXAMPLE JSON OUTPUT:
{{
"reasoning": "This is where you explain your reasoning for the decision you made.",
"decision": "Will be either "include" or "exclude"."
}}
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Is there a service charge for delivery or takeout orders?
### TASK ###
You are responsible for making a decision on whether the venue information document is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
### CROSSOVER TOPICS THAT ARE NOT IN THE VENUE INFORMATION DOCUMENT ###
ALL QUERIES HANDLED BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE VENUE INFORMATION DOCUMENT FROM THE CONTEXT.
If these arise note that the menu doc would NOT be needed as the answer will lie elsewhere, outside of your scope;
RESERVATIONS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
Information on the reservation policies of the venue, this includes;
- Walk in customers seating policy.
- Minimum spends for reserved areas.
- Time limits on reservations.
- Cancellation policys (regarding late arrivals or no shows).
- How groups and large booking are handled.
Other detailed information includes;
- Detailed information on the seating layouts and descriptive information about the different parts of the venue which can be used to compare against the customers requested group size.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
UPCOMING EVENTS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information on the date, time, whether a ticket is needed, and a brief description of the event. Also rules and policies surrounding the specific events.
Any Information asking about upcoming events planned by the business should be referred onto the upcoming events document and thus exclude the venue information document.
MENU DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Pricing ,Ingredients and descriptions of all menu items.(It goes without saying availibility of menu items is not in the venue information document).
- This covers all food, drink and shisha related queries.
- Delivery availability of products, including services like Uber Eats or Foodpanda.
- Takeway of menu items policy.
- Customization of menu items.
- Special offers or happy hours.
- Last orders time for all menu items.
OPENING HOURS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- The 7 day regular working schedule of the venue. Is covered in the opening hours document.
- Last orders time and subsequent closing time for the kitchen, bar etc. Are covered in the opening hours document. Not the venue information document.
Any query that is answered by the opening hours document should not include the venue information document as it would be irrelevant context.
ALL OF THE QUERIES WHICH ARE DIRECTLY ANSWERABLE BY THE CORSSOVER TOPICS SHOULD NOT INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT.
### GUIDELINES ###
If a query asks about a "dining hall", a "theatre" or "bar" or anything that relates to a physical space. We will need the venue information to check if the venue has that space or not. We are not just including conntext to directly answer the querybut also to fact-check if the assumptions made in the query were correct.
Furthermore if the query mentions restrooms, or other facilities that are part of the physical space, the venue informationdocument should be included in the context regardless of the crux of the query.
EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY, IF IT MENTIONS A PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE, THE VENUE INFORMATION DOCUMENT SHOULD BE INCLUDED IN THE CONTEXT.
If a customer mentions wanting to do some form of activity at the venue, like reading a book, studying, working, or having a meeting. The venue information document should be included in the context. As the next node will need to know if the venue has the space to accomodate the customer's request but more importantly it give context on the interior style and ambiance and whether said activity is suitiable.
For example if a customer asks whether its possible to book a private event, the venue information is needed to provide a full a comprehensive answer. As if included, the next node will now be able to provide information on the venues spaces, ammenities and other parts of the physical space that would make it suitiable or not for a private event or custom booking.
The worst case scenario is a customer arrives for a booking but the venue cannot accomodate them due to a policy or physical constraint that was not considered in the response.
<｜Assistant｜>
<think>
Okay, let's tackle this query: "Is there a service charge for delivery or takeout orders?"
First, I need to check if the venue information document is relevant. The service charge is listed in the venue document's contents. The query specifically mentions delivery or takeout, which according to the guidelines, the menu document handles takeout policies and delivery availability. However, since the query is about service charges, the venue information document should be included as it contains the relevant details about service charges.
</think>
{
"reasoning": "The query asks about service charges for delivery or takeout orders. While the menu document handles takeout policies and delivery availability, the service charge information is specifically mentioned in the venue information document. Therefore, the venue information document should be included to provide the necessary details about service charges.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the venue information document in the prompt is relevant for answering the user query. Ensure you take proper care and consideration to ensure you do not make the wrong decision.
To ensure you are able to make the correct decision, here is a breakdown of what is covered in the venue information document:
VENUE INFORMATION DOCUMENT CONTENTS:
- An abstract/blurb describing the venue.
- Information on location and accessability.
- Information on parking at the venue.
- Interior design and ambiance.
- The seating layout and capacity of the venue.
- The facilities and ammenities available at the venue(eg. wifi, ventillation system, sound system, projectors, restrooms facilites).
- All Information that is related to the physial space wil be in this document - this includes the dining area, bar, theatre, restrooms etc.
- Contact information for additional more complex queries.
- Service charges & all other additional charges.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Dress code.
- Minimum age restrictions.
- Minimum spend policy.
- Rules around patrons using their own decorations on reserved areas.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query is in one of the listed crossover topics, you exclude the document. The reasoning will be explained in the prompt.
The food and drink policy within the venue information document ONLY COVERS the rules and policies around bring in outside food and drinks. And storing unfinished alcohol. All food and drink policy outside of this can be considered crossover topics and will be handled in the menu document.
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude.
The venue information document does NOT have any information about the opening times of the venue. Queries about opening hours are thus a crossover topic and will be handled in the opening hours document.
ALL QUERIES THAT MENTION ANY PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE SHOULD INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT. EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in json format.
Ensure you follow the following json schema no matter the document or query you are working with:
EXAMPLE JSON OUTPUT:
{{
"reasoning": "This is where you explain your reasoning for the decision you made.",
"decision": "Will be either "include" or "exclude"."
}}
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
What’s the tax percentage applied to my order?
### TASK ###
You are responsible for making a decision on whether the venue information document is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
### CROSSOVER TOPICS THAT ARE NOT IN THE VENUE INFORMATION DOCUMENT ###
ALL QUERIES HANDLED BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE VENUE INFORMATION DOCUMENT FROM THE CONTEXT.
If these arise note that the menu doc would NOT be needed as the answer will lie elsewhere, outside of your scope;
RESERVATIONS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
Information on the reservation policies of the venue, this includes;
- Walk in customers seating policy.
- Minimum spends for reserved areas.
- Time limits on reservations.
- Cancellation policys (regarding late arrivals or no shows).
- How groups and large booking are handled.
Other detailed information includes;
- Detailed information on the seating layouts and descriptive information about the different parts of the venue which can be used to compare against the customers requested group size.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
UPCOMING EVENTS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information on the date, time, whether a ticket is needed, and a brief description of the event. Also rules and policies surrounding the specific events.
Any Information asking about upcoming events planned by the business should be referred onto the upcoming events document and thus exclude the venue information document.
MENU DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Pricing ,Ingredients and descriptions of all menu items.(It goes without saying availibility of menu items is not in the venue information document).
- This covers all food, drink and shisha related queries.
- Delivery availability of products, including services like Uber Eats or Foodpanda.
- Takeway of menu items policy.
- Customization of menu items.
- Special offers or happy hours.
- Last orders time for all menu items.
OPENING HOURS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- The 7 day regular working schedule of the venue. Is covered in the opening hours document.
- Last orders time and subsequent closing time for the kitchen, bar etc. Are covered in the opening hours document. Not the venue information document.
Any query that is answered by the opening hours document should not include the venue information document as it would be irrelevant context.
ALL OF THE QUERIES WHICH ARE DIRECTLY ANSWERABLE BY THE CORSSOVER TOPICS SHOULD NOT INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT.
### GUIDELINES ###
If a query asks about a "dining hall", a "theatre" or "bar" or anything that relates to a physical space. We will need the venue information to check if the venue has that space or not. We are not just including conntext to directly answer the querybut also to fact-check if the assumptions made in the query were correct.
Furthermore if the query mentions restrooms, or other facilities that are part of the physical space, the venue informationdocument should be included in the context regardless of the crux of the query.
EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY, IF IT MENTIONS A PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE, THE VENUE INFORMATION DOCUMENT SHOULD BE INCLUDED IN THE CONTEXT.
If a customer mentions wanting to do some form of activity at the venue, like reading a book, studying, working, or having a meeting. The venue information document should be included in the context. As the next node will need to know if the venue has the space to accomodate the customer's request but more importantly it give context on the interior style and ambiance and whether said activity is suitiable.
For example if a customer asks whether its possible to book a private event, the venue information is needed to provide a full a comprehensive answer. As if included, the next node will now be able to provide information on the venues spaces, ammenities and other parts of the physical space that would make it suitiable or not for a private event or custom booking.
The worst case scenario is a customer arrives for a booking but the venue cannot accomodate them due to a policy or physical constraint that was not considered in the response.
<｜Assistant｜>
<think>
Alright, let's tackle this query: "What’s the tax percentage applied to my order?" I need to determine if the venue information document is relevant.
First, the user is asking about tax percentage on an order. Tax rates typically relate to menu items or services provided, which would fall under the menu document. The venue information document covers service charges and additional fees, which additional taxes would come under.
Looking at the crossover topics, the venue information document handles service charges and additional fees, including taxes. So the answer lies there. Also, the query doesn't mention any physical spaces or facilities. No references to the bar, seating, or amenities that would require venue info.
The fact that we need the service charge and other additiaonl charges infor is enough to justify the inclusion of the venue information document.
</think>
{
"reasoning": "The query asks about the tax percentage applied to orders, which pertains to pricing policies for menu items. The venue information document covers service charges and additional fees, which would include tax percentages. Additionally, the query does not mention any physical spaces, facilities, policies (e.g., service charges, tipping), or venue-specific constraints that would require context from the venue information document. But, since this is related to service charges and additional fees, the venue information document is essential here.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the venue information document in the prompt is relevant for answering the user query. Ensure you take proper care and consideration to ensure you do not make the wrong decision.
To ensure you are able to make the correct decision, here is a breakdown of what is covered in the venue information document:
VENUE INFORMATION DOCUMENT CONTENTS:
- An abstract/blurb describing the venue.
- Information on location and accessability.
- Information on parking at the venue.
- Interior design and ambiance.
- The seating layout and capacity of the venue.
- The facilities and ammenities available at the venue(eg. wifi, ventillation system, sound system, projectors, restrooms facilites).
- All Information that is related to the physial space wil be in this document - this includes the dining area, bar, theatre, restrooms etc.
- Contact information for additional more complex queries.
- Service charges & all other additional charges.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Dress code.
- Minimum age restrictions.
- Minimum spend policy.
- Rules around patrons using their own decorations on reserved areas.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query is in one of the listed crossover topics, you exclude the document. The reasoning will be explained in the prompt.
The food and drink policy within the venue information document ONLY COVERS the rules and policies around bring in outside food and drinks. And storing unfinished alcohol. All food and drink policy outside of this can be considered crossover topics and will be handled in the menu document.
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude.
The venue information document does NOT have any information about the opening times of the venue. Queries about opening hours are thus a crossover topic and will be handled in the opening hours document.
ALL QUERIES THAT MENTION ANY PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE SHOULD INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT. EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in json format.
Ensure you follow the following json schema no matter the document or query you are working with:
EXAMPLE JSON OUTPUT:
{{
"reasoning": "This is where you explain your reasoning for the decision you made.",
"decision": "Will be either "include" or "exclude"."
}}
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
how much needs to be left i ntheb ottle to be able to store it
### TASK ###
You are responsible for making a decision on whether the venue information document is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
### CROSSOVER TOPICS THAT ARE NOT IN THE VENUE INFORMATION DOCUMENT ###
ALL QUERIES HANDLED BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE VENUE INFORMATION DOCUMENT FROM THE CONTEXT.
If these arise note that the menu doc would NOT be needed as the answer will lie elsewhere, outside of your scope;
RESERVATIONS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
Information on the reservation policies of the venue, this includes;
- Walk in customers seating policy.
- Minimum spends for reserved areas.
- Time limits on reservations.
- Cancellation policys (regarding late arrivals or no shows).
- How groups and large booking are handled.
Other detailed information includes;
- Detailed information on the seating layouts and descriptive information about the different parts of the venue which can be used to compare against the customers requested group size.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
UPCOMING EVENTS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information on the date, time, whether a ticket is needed, and a brief description of the event. Also rules and policies surrounding the specific events.
Any Information asking about upcoming events planned by the business should be referred onto the upcoming events document and thus exclude the venue information document.
MENU DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Pricing ,Ingredients and descriptions of all menu items.(It goes without saying availibility of menu items is not in the venue information document).
- This covers all food, drink and shisha related queries.
- Delivery availability of products, including services like Uber Eats or Foodpanda.
- Takeway of menu items policy.
- Customization of menu items.
- Special offers or happy hours.
- Last orders time for all menu items.
OPENING HOURS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- The 7 day regular working schedule of the venue. Is covered in the opening hours document.
- Last orders time and subsequent closing time for the kitchen, bar etc. Are covered in the opening hours document. Not the venue information document.
Any query that is answered by the opening hours document should not include the venue information document as it would be irrelevant context.
ALL OF THE QUERIES WHICH ARE DIRECTLY ANSWERABLE BY THE CORSSOVER TOPICS SHOULD NOT INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT.
### GUIDELINES ###
If a query asks about a "dining hall", a "theatre" or "bar" or anything that relates to a physical space. We will need the venue information to check if the venue has that space or not. We are not just including conntext to directly answer the querybut also to fact-check if the assumptions made in the query were correct.
Furthermore if the query mentions restrooms, or other facilities that are part of the physical space, the venue informationdocument should be included in the context regardless of the crux of the query.
EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY, IF IT MENTIONS A PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE, THE VENUE INFORMATION DOCUMENT SHOULD BE INCLUDED IN THE CONTEXT.
If a customer mentions wanting to do some form of activity at the venue, like reading a book, studying, working, or having a meeting. The venue information document should be included in the context. As the next node will need to know if the venue has the space to accomodate the customer's request but more importantly it give context on the interior style and ambiance and whether said activity is suitiable.
For example if a customer asks whether its possible to book a private event, the venue information is needed to provide a full a comprehensive answer. As if included, the next node will now be able to provide information on the venues spaces, ammenities and other parts of the physical space that would make it suitiable or not for a private event or custom booking.
The worst case scenario is a customer arrives for a booking but the venue cannot accomodate them due to a policy or physical constraint that was not considered in the response.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "how much needs to be left in the bottle to be able to store it." From what I understand, they're referring to storing unfinished alcohol. The venue information document covers the rules around storing unfinished alcohol, as mentioned in its contents. The guidelines say that food and drink policies in the venue document only include rules on bringing outside items and storing alcohol. Since this query is directly about the policy for storing leftover alcohol, which is explicitly covered in the venue info, I should include it. There's no mention of crossover topics here like menu items or reservations, so no exclusion needed. The key point is the policy on storing alcohol, which is part of the venue's rules.
</think>
{
"reasoning": "The query asks about the policy regarding storing unfinished alcohol, specifically the minimum amount required to be left in the bottle. The venue information document explicitly covers 'Rules on storing unfinished alcohol for later consumption' as part of its contents. This is a core policy directly addressed in the venue information document and does not fall under the crossover topics like menu items, reservations, events, or opening hours. Therefore, the venue information document is relevant for answering this query.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the venue information document in the prompt is relevant for answering the user query. Ensure you take proper care and consideration to ensure you do not make the wrong decision.
To ensure you are able to make the correct decision, here is a breakdown of what is covered in the venue information document:
VENUE INFORMATION DOCUMENT CONTENTS:
- An abstract/blurb describing the venue.
- Information on location and accessability.
- Information on parking at the venue.
- Interior design and ambiance.
- The seating layout and capacity of the venue.
- The facilities and ammenities available at the venue(eg. wifi, ventillation system, sound system, projectors, restrooms facilites).
- All Information that is related to the physial space wil be in this document - this includes the dining area, bar, theatre, restrooms etc.
- Contact information for additional more complex queries.
- Service charges & all other additional charges.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Dress code.
- Minimum age restrictions.
- Minimum spend policy.
- Rules around patrons using their own decorations on reserved areas.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query is in one of the listed crossover topics, you exclude the document. The reasoning will be explained in the prompt.
The food and drink policy within the venue information document ONLY COVERS the rules and policies around bring in outside food and drinks. And storing unfinished alcohol. All food and drink policy outside of this can be considered crossover topics and will be handled in the menu document.
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude.
The venue information document does NOT have any information about the opening times of the venue. Queries about opening hours are thus a crossover topic and will be handled in the opening hours document.
ALL QUERIES THAT MENTION ANY PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE SHOULD INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT. EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in json format.
Ensure you follow the following json schema no matter the document or query you are working with:
EXAMPLE JSON OUTPUT:
{{
"reasoning": "This is where you explain your reasoning for the decision you made.",
"decision": "Will be either "include" or "exclude"."
}}
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
can I store unfinished bottle for next itme I come
### TASK ###
You are responsible for making a decision on whether the venue information document is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
### CROSSOVER TOPICS THAT ARE NOT IN THE VENUE INFORMATION DOCUMENT ###
ALL QUERIES HANDLED BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE VENUE INFORMATION DOCUMENT FROM THE CONTEXT.
If these arise note that the menu doc would NOT be needed as the answer will lie elsewhere, outside of your scope;
RESERVATIONS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
Information on the reservation policies of the venue, this includes;
- Walk in customers seating policy.
- Minimum spends for reserved areas.
- Time limits on reservations.
- Cancellation policys (regarding late arrivals or no shows).
- How groups and large booking are handled.
Other detailed information includes;
- Detailed information on the seating layouts and descriptive information about the different parts of the venue which can be used to compare against the customers requested group size.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
UPCOMING EVENTS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information on the date, time, whether a ticket is needed, and a brief description of the event. Also rules and policies surrounding the specific events.
Any Information asking about upcoming events planned by the business should be referred onto the upcoming events document and thus exclude the venue information document.
MENU DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Pricing ,Ingredients and descriptions of all menu items.(It goes without saying availibility of menu items is not in the venue information document).
- This covers all food, drink and shisha related queries.
- Delivery availability of products, including services like Uber Eats or Foodpanda.
- Takeway of menu items policy.
- Customization of menu items.
- Special offers or happy hours.
- Last orders time for all menu items.
OPENING HOURS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- The 7 day regular working schedule of the venue. Is covered in the opening hours document.
- Last orders time and subsequent closing time for the kitchen, bar etc. Are covered in the opening hours document. Not the venue information document.
Any query that is answered by the opening hours document should not include the venue information document as it would be irrelevant context.
ALL OF THE QUERIES WHICH ARE DIRECTLY ANSWERABLE BY THE CORSSOVER TOPICS SHOULD NOT INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT.
### GUIDELINES ###
If a query asks about a "dining hall", a "theatre" or "bar" or anything that relates to a physical space. We will need the venue information to check if the venue has that space or not. We are not just including conntext to directly answer the querybut also to fact-check if the assumptions made in the query were correct.
Furthermore if the query mentions restrooms, or other facilities that are part of the physical space, the venue informationdocument should be included in the context regardless of the crux of the query.
EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY, IF IT MENTIONS A PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE, THE VENUE INFORMATION DOCUMENT SHOULD BE INCLUDED IN THE CONTEXT.
If a customer mentions wanting to do some form of activity at the venue, like reading a book, studying, working, or having a meeting. The venue information document should be included in the context. As the next node will need to know if the venue has the space to accomodate the customer's request but more importantly it give context on the interior style and ambiance and whether said activity is suitiable.
For example if a customer asks whether its possible to book a private event, the venue information is needed to provide a full a comprehensive answer. As if included, the next node will now be able to provide information on the venues spaces, ammenities and other parts of the physical space that would make it suitiable or not for a private event or custom booking.
The worst case scenario is a customer arrives for a booking but the venue cannot accomodate them due to a policy or physical constraint that was not considered in the response.
<｜Assistant｜>
<think>
Okay, let's look at the user's query: "can I store unfinished bottle for next itme I come". They're asking about storing an unfinished bottle for their next visit.
First, I need to check what the venue information document covers. According to the guidelines, the venue information includes rules around storing unfinished alcohol. That's explicitly listed under the document's contents.
Looking at the crossover topics, this doesn't fall under reservations, upcoming events, menu, or opening hours. The query is specifically about the venue's policy on storing alcohol, which is part of the venue information. Even though there's a typo in "next itme", the intent is clear.
The guidelines also mention that any policy related to bringing outside food/drink or storing alcohol is covered here. There's no mention of a physical space here, but since the policy is part of the venue information, the answer lies there.
Other documents like the menu cover food and drink items but not storage policies. The reservation document handles booking-related policies, which isn't the case here. Therefore, including the venue information document is necessary to accurately answer the user's question about storing their bottle.
</think>
{
"reasoning": "The user is asking about storing an unfinished bottle for their next visit, which directly relates to the venue's policy on storing unfinished alcohol. According to the venue information document's contents, this falls under 'Rules on storing unfinished alcohol for later consumption'. This policy is explicitly covered in the venue information document and does not overlap with crossover topics handled by other documents like reservations, menu, or opening hours. Therefore, the venue information document is relevant and necessary to answer this query.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the venue information document in the prompt is relevant for answering the user query. Ensure you take proper care and consideration to ensure you do not make the wrong decision.
To ensure you are able to make the correct decision, here is a breakdown of what is covered in the venue information document:
VENUE INFORMATION DOCUMENT CONTENTS:
- An abstract/blurb describing the venue.
- Information on location and accessability.
- Information on parking at the venue.
- Interior design and ambiance.
- The seating layout and capacity of the venue.
- The facilities and ammenities available at the venue(eg. wifi, ventillation system, sound system, projectors, restrooms facilites).
- All Information that is related to the physial space wil be in this document - this includes the dining area, bar, theatre, restrooms etc.
- Contact information for additional more complex queries.
- Service charges & all other additional charges.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Dress code.
- Minimum age restrictions.
- Minimum spend policy.
- Rules around patrons using their own decorations on reserved areas.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query is in one of the listed crossover topics, you exclude the document. The reasoning will be explained in the prompt.
The food and drink policy within the venue information document ONLY COVERS the rules and policies around bring in outside food and drinks. And storing unfinished alcohol. All food and drink policy outside of this can be considered crossover topics and will be handled in the menu document.
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude.
The venue information document does NOT have any information about the opening times of the venue. Queries about opening hours are thus a crossover topic and will be handled in the opening hours document.
ALL QUERIES THAT MENTION ANY PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE SHOULD INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT. EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in json format.
Ensure you follow the following json schema no matter the document or query you are working with:
EXAMPLE JSON OUTPUT:
{{
"reasoning": "This is where you explain your reasoning for the decision you made.",
"decision": "Will be either "include" or "exclude"."
}}
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you allow customers to take unfinished cocktails home?
### TASK ###
You are responsible for making a decision on whether the venue information document is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
### CROSSOVER TOPICS THAT ARE NOT IN THE VENUE INFORMATION DOCUMENT ###
ALL QUERIES HANDLED BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE VENUE INFORMATION DOCUMENT FROM THE CONTEXT.
If these arise note that the menu doc would NOT be needed as the answer will lie elsewhere, outside of your scope;
RESERVATIONS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
Information on the reservation policies of the venue, this includes;
- Walk in customers seating policy.
- Minimum spends for reserved areas.
- Time limits on reservations.
- Cancellation policys (regarding late arrivals or no shows).
- How groups and large booking are handled.
Other detailed information includes;
- Detailed information on the seating layouts and descriptive information about the different parts of the venue which can be used to compare against the customers requested group size.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
UPCOMING EVENTS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information on the date, time, whether a ticket is needed, and a brief description of the event. Also rules and policies surrounding the specific events.
Any Information asking about upcoming events planned by the business should be referred onto the upcoming events document and thus exclude the venue information document.
MENU DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Pricing ,Ingredients and descriptions of all menu items.(It goes without saying availibility of menu items is not in the venue information document).
- This covers all food, drink and shisha related queries.
- Delivery availability of products, including services like Uber Eats or Foodpanda.
- Takeway of menu items policy.
- Customization of menu items.
- Special offers or happy hours.
- Last orders time for all menu items.
OPENING HOURS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- The 7 day regular working schedule of the venue. Is covered in the opening hours document.
- Last orders time and subsequent closing time for the kitchen, bar etc. Are covered in the opening hours document. Not the venue information document.
Any query that is answered by the opening hours document should not include the venue information document as it would be irrelevant context.
ALL OF THE QUERIES WHICH ARE DIRECTLY ANSWERABLE BY THE CORSSOVER TOPICS SHOULD NOT INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT.
### GUIDELINES ###
If a query asks about a "dining hall", a "theatre" or "bar" or anything that relates to a physical space. We will need the venue information to check if the venue has that space or not. We are not just including conntext to directly answer the querybut also to fact-check if the assumptions made in the query were correct.
Furthermore if the query mentions restrooms, or other facilities that are part of the physical space, the venue informationdocument should be included in the context regardless of the crux of the query.
EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY, IF IT MENTIONS A PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE, THE VENUE INFORMATION DOCUMENT SHOULD BE INCLUDED IN THE CONTEXT.
If a customer mentions wanting to do some form of activity at the venue, like reading a book, studying, working, or having a meeting. The venue information document should be included in the context. As the next node will need to know if the venue has the space to accomodate the customer's request but more importantly it give context on the interior style and ambiance and whether said activity is suitiable.
For example if a customer asks whether its possible to book a private event, the venue information is needed to provide a full a comprehensive answer. As if included, the next node will now be able to provide information on the venues spaces, ammenities and other parts of the physical space that would make it suitiable or not for a private event or custom booking.
The worst case scenario is a customer arrives for a booking but the venue cannot accomodate them due to a policy or physical constraint that was not considered in the response.
<｜Assistant｜>
<think>
Okay, let's tackle this query: "Do you allow customers to take unfinished cocktails home?"
First, I need to check which document covers this. The user is asking about taking home unfinished cocktails, which relates to the venue's policy on storing or taking away alcohol. The guidelines mention that the venue information document includes rules around storing unfinished alcohol. The menu document, on the other hand, handles takeaway policies for menu items, but this isn't about ordering takeaway; it's about taking leftover drinks. Since the question is specifically about the policy regarding unfinished cocktails, the answer should be in the venue information document.
Also, the query doesn't mention any crossover topics like reservations, events, menu items, or opening hours. It's purely about the venue's policy, so the venue document is relevant here. Even if the answer was in another document, the guidelines say to include venue info if it's about physical space or policies covered there. In this case, storing unfinished alcohol is covered under venue policies. Therefore, include the venue information document.
</think>
{
"reasoning": "The query asks about the policy regarding taking unfinished cocktails home. The venue information document explicitly covers rules around storing unfinished alcohol for later consumption. This falls under the venue's policies, which are detailed in the venue information document. The menu document handles takeaway policies for menu items, but this specific policy about unfinished drinks is a venue policy, not a menu item policy. Therefore, the venue information document is relevant and should be included.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the venue information document in the prompt is relevant for answering the user query. Ensure you take proper care and consideration to ensure you do not make the wrong decision.
To ensure you are able to make the correct decision, here is a breakdown of what is covered in the venue information document:
VENUE INFORMATION DOCUMENT CONTENTS:
- An abstract/blurb describing the venue.
- Information on location and accessability.
- Information on parking at the venue.
- Interior design and ambiance.
- The seating layout and capacity of the venue.
- The facilities and ammenities available at the venue(eg. wifi, ventillation system, sound system, projectors, restrooms facilites).
- All Information that is related to the physial space wil be in this document - this includes the dining area, bar, theatre, restrooms etc.
- Contact information for additional more complex queries.
- Service charges & all other additional charges.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Dress code.
- Minimum age restrictions.
- Minimum spend policy.
- Rules around patrons using their own decorations on reserved areas.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query is in one of the listed crossover topics, you exclude the document. The reasoning will be explained in the prompt.
The food and drink policy within the venue information document ONLY COVERS the rules and policies around bring in outside food and drinks. And storing unfinished alcohol. All food and drink policy outside of this can be considered crossover topics and will be handled in the menu document.
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude.
The venue information document does NOT have any information about the opening times of the venue. Queries about opening hours are thus a crossover topic and will be handled in the opening hours document.
ALL QUERIES THAT MENTION ANY PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE SHOULD INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT. EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in json format.
Ensure you follow the following json schema no matter the document or query you are working with:
EXAMPLE JSON OUTPUT:
{{
"reasoning": "This is where you explain your reasoning for the decision you made.",
"decision": "Will be either "include" or "exclude"."
}}
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
What happens if I don’t finish my wine during my visit?
### TASK ###
You are responsible for making a decision on whether the venue information document is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
### CROSSOVER TOPICS THAT ARE NOT IN THE VENUE INFORMATION DOCUMENT ###
ALL QUERIES HANDLED BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE VENUE INFORMATION DOCUMENT FROM THE CONTEXT.
If these arise note that the menu doc would NOT be needed as the answer will lie elsewhere, outside of your scope;
RESERVATIONS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
Information on the reservation policies of the venue, this includes;
- Walk in customers seating policy.
- Minimum spends for reserved areas.
- Time limits on reservations.
- Cancellation policys (regarding late arrivals or no shows).
- How groups and large booking are handled.
Other detailed information includes;
- Detailed information on the seating layouts and descriptive information about the different parts of the venue which can be used to compare against the customers requested group size.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
UPCOMING EVENTS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information on the date, time, whether a ticket is needed, and a brief description of the event. Also rules and policies surrounding the specific events.
Any Information asking about upcoming events planned by the business should be referred onto the upcoming events document and thus exclude the venue information document.
MENU DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Pricing ,Ingredients and descriptions of all menu items.(It goes without saying availibility of menu items is not in the venue information document).
- This covers all food, drink and shisha related queries.
- Delivery availability of products, including services like Uber Eats or Foodpanda.
- Takeway of menu items policy.
- Customization of menu items.
- Special offers or happy hours.
- Last orders time for all menu items.
OPENING HOURS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- The 7 day regular working schedule of the venue. Is covered in the opening hours document.
- Last orders time and subsequent closing time for the kitchen, bar etc. Are covered in the opening hours document. Not the venue information document.
Any query that is answered by the opening hours document should not include the venue information document as it would be irrelevant context.
ALL OF THE QUERIES WHICH ARE DIRECTLY ANSWERABLE BY THE CORSSOVER TOPICS SHOULD NOT INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT.
### GUIDELINES ###
If a query asks about a "dining hall", a "theatre" or "bar" or anything that relates to a physical space. We will need the venue information to check if the venue has that space or not. We are not just including conntext to directly answer the querybut also to fact-check if the assumptions made in the query were correct.
Furthermore if the query mentions restrooms, or other facilities that are part of the physical space, the venue informationdocument should be included in the context regardless of the crux of the query.
EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY, IF IT MENTIONS A PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE, THE VENUE INFORMATION DOCUMENT SHOULD BE INCLUDED IN THE CONTEXT.
If a customer mentions wanting to do some form of activity at the venue, like reading a book, studying, working, or having a meeting. The venue information document should be included in the context. As the next node will need to know if the venue has the space to accomodate the customer's request but more importantly it give context on the interior style and ambiance and whether said activity is suitiable.
For example if a customer asks whether its possible to book a private event, the venue information is needed to provide a full a comprehensive answer. As if included, the next node will now be able to provide information on the venues spaces, ammenities and other parts of the physical space that would make it suitiable or not for a private event or custom booking.
The worst case scenario is a customer arrives for a booking but the venue cannot accomodate them due to a policy or physical constraint that was not considered in the response.
<｜Assistant｜>
<think>
Okay, let's see. The user is asking, "What happens if I don’t finish my wine during my visit?" I need to check if the venue information document is relevant here.
First, the venue information document covers policies like bringing outside food/drinks and storing unfinished alcohol. The query is about not finishing wine, which would fall under the policy of storing unfinished alcohol. That's definitely part of the venue's rules, so the venue document should have this information.
I should also check if this is a crossover topic. The menu document deals with food and drink items, their availability, pricing, etc., but not the policies on storing leftovers. The reservation, events, and opening hours documents don't apply here either. Since the question is about a policy related to alcohol consumption on-site, it's covered in the venue info.
Additionally, even though the query mentions wine (a drink), it's about the venue's policy, not the menu item itself. The guidelines say that the venue document includes rules on storing unfinished alcohol. No mention of physical spaces here, but the policy is clearly within the venue document's scope. So, include the venue information document.
</think>
{
"reasoning": "The query asks about the policy regarding unfinished wine, which directly relates to the venue's rules on storing unfinished alcohol. The venue information document explicitly covers this policy, making it essential for answering the user's question. While the menu document handles food and drink items, this query pertains to a venue-specific policy rather than product details, thus excluding crossover topics.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the venue information document in the prompt is relevant for answering the user query. Ensure you take proper care and consideration to ensure you do not make the wrong decision.
To ensure you are able to make the correct decision, here is a breakdown of what is covered in the venue information document:
VENUE INFORMATION DOCUMENT CONTENTS:
- An abstract/blurb describing the venue.
- Information on location and accessability.
- Information on parking at the venue.
- Interior design and ambiance.
- The seating layout and capacity of the venue.
- The facilities and ammenities available at the venue(eg. wifi, ventillation system, sound system, projectors, restrooms facilites).
- All Information that is related to the physial space wil be in this document - this includes the dining area, bar, theatre, restrooms etc.
- Contact information for additional more complex queries.
- Service charges & all other additional charges.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Dress code.
- Minimum age restrictions.
- Minimum spend policy.
- Rules around patrons using their own decorations on reserved areas.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query is in one of the listed crossover topics, you exclude the document. The reasoning will be explained in the prompt.
The food and drink policy within the venue information document ONLY COVERS the rules and policies around bring in outside food and drinks. And storing unfinished alcohol. All food and drink policy outside of this can be considered crossover topics and will be handled in the menu document.
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude.
The venue information document does NOT have any information about the opening times of the venue. Queries about opening hours are thus a crossover topic and will be handled in the opening hours document.
ALL QUERIES THAT MENTION ANY PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE SHOULD INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT. EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in json format.
Ensure you follow the following json schema no matter the document or query you are working with:
EXAMPLE JSON OUTPUT:
{{
"reasoning": "This is where you explain your reasoning for the decision you made.",
"decision": "Will be either "include" or "exclude"."
}}
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you allow guests to return for unfinished drinks on a later visit?
### TASK ###
You are responsible for making a decision on whether the venue information document is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
### CROSSOVER TOPICS THAT ARE NOT IN THE VENUE INFORMATION DOCUMENT ###
ALL QUERIES HANDLED BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE VENUE INFORMATION DOCUMENT FROM THE CONTEXT.
If these arise note that the menu doc would NOT be needed as the answer will lie elsewhere, outside of your scope;
RESERVATIONS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
Information on the reservation policies of the venue, this includes;
- Walk in customers seating policy.
- Minimum spends for reserved areas.
- Time limits on reservations.
- Cancellation policys (regarding late arrivals or no shows).
- How groups and large booking are handled.
Other detailed information includes;
- Detailed information on the seating layouts and descriptive information about the different parts of the venue which can be used to compare against the customers requested group size.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
UPCOMING EVENTS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information on the date, time, whether a ticket is needed, and a brief description of the event. Also rules and policies surrounding the specific events.
Any Information asking about upcoming events planned by the business should be referred onto the upcoming events document and thus exclude the venue information document.
MENU DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Pricing ,Ingredients and descriptions of all menu items.(It goes without saying availibility of menu items is not in the venue information document).
- This covers all food, drink and shisha related queries.
- Delivery availability of products, including services like Uber Eats or Foodpanda.
- Takeway of menu items policy.
- Customization of menu items.
- Special offers or happy hours.
- Last orders time for all menu items.
OPENING HOURS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- The 7 day regular working schedule of the venue. Is covered in the opening hours document.
- Last orders time and subsequent closing time for the kitchen, bar etc. Are covered in the opening hours document. Not the venue information document.
Any query that is answered by the opening hours document should not include the venue information document as it would be irrelevant context.
ALL OF THE QUERIES WHICH ARE DIRECTLY ANSWERABLE BY THE CORSSOVER TOPICS SHOULD NOT INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT.
### GUIDELINES ###
If a query asks about a "dining hall", a "theatre" or "bar" or anything that relates to a physical space. We will need the venue information to check if the venue has that space or not. We are not just including conntext to directly answer the querybut also to fact-check if the assumptions made in the query were correct.
Furthermore if the query mentions restrooms, or other facilities that are part of the physical space, the venue informationdocument should be included in the context regardless of the crux of the query.
EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY, IF IT MENTIONS A PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE, THE VENUE INFORMATION DOCUMENT SHOULD BE INCLUDED IN THE CONTEXT.
If a customer mentions wanting to do some form of activity at the venue, like reading a book, studying, working, or having a meeting. The venue information document should be included in the context. As the next node will need to know if the venue has the space to accomodate the customer's request but more importantly it give context on the interior style and ambiance and whether said activity is suitiable.
For example if a customer asks whether its possible to book a private event, the venue information is needed to provide a full a comprehensive answer. As if included, the next node will now be able to provide information on the venues spaces, ammenities and other parts of the physical space that would make it suitiable or not for a private event or custom booking.
The worst case scenario is a customer arrives for a booking but the venue cannot accomodate them due to a policy or physical constraint that was not considered in the response.
<｜Assistant｜>
<think>
Okay, let me analyze this query. The user is asking if they can return later to finish their drinks.
Looking at the venue information document's contents, there's a section about storing unfinished alcohol. The query specifically asks about returning for unfinished drinks, which aligns with the venue's policy on storing alcohol.
The guidelines mention that even if the query is about something else, if it's related to the venue's policies (like food and drink storage), the document should be included. Since this is a policy question and falls under the venue's rules, it's covered here.
No crossover topics like reservations, events, menu, or opening hours are involved here. So, the decision is to include the venue information document.
</think>
{
"reasoning": "The query asks about the venue's policy regarding returning to consume unfinished drinks on a later visit. The venue information document explicitly covers 'Rules around storing unfinished alcohol for later consumption', which directly addresses this query. Since this is a policy related to handling unfinished drinks within the venue's guidelines, the document is relevant. There is no mention of crossover topics like reservations, events, menu items, or opening hours that would require exclusion.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the venue information document in the prompt is relevant for answering the user query. Ensure you take proper care and consideration to ensure you do not make the wrong decision.
To ensure you are able to make the correct decision, here is a breakdown of what is covered in the venue information document:
VENUE INFORMATION DOCUMENT CONTENTS:
- An abstract/blurb describing the venue.
- Information on location and accessability.
- Information on parking at the venue.
- Interior design and ambiance.
- The seating layout and capacity of the venue.
- The facilities and ammenities available at the venue(eg. wifi, ventillation system, sound system, projectors, restrooms facilites).
- All Information that is related to the physial space wil be in this document - this includes the dining area, bar, theatre, restrooms etc.
- Contact information for additional more complex queries.
- Service charges & all other additional charges.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Dress code.
- Minimum age restrictions.
- Minimum spend policy.
- Rules around patrons using their own decorations on reserved areas.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query is in one of the listed crossover topics, you exclude the document. The reasoning will be explained in the prompt.
The food and drink policy within the venue information document ONLY COVERS the rules and policies around bring in outside food and drinks. And storing unfinished alcohol. All food and drink policy outside of this can be considered crossover topics and will be handled in the menu document.
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude.
The venue information document does NOT have any information about the opening times of the venue. Queries about opening hours are thus a crossover topic and will be handled in the opening hours document.
ALL QUERIES THAT MENTION ANY PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE SHOULD INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT. EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in json format.
Ensure you follow the following json schema no matter the document or query you are working with:
EXAMPLE JSON OUTPUT:
{{
"reasoning": "This is where you explain your reasoning for the decision you made.",
"decision": "Will be either "include" or "exclude"."
}}
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I store an unfinished drink for later in the evening?
### TASK ###
You are responsible for making a decision on whether the venue information document is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
### CROSSOVER TOPICS THAT ARE NOT IN THE VENUE INFORMATION DOCUMENT ###
ALL QUERIES HANDLED BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE VENUE INFORMATION DOCUMENT FROM THE CONTEXT.
If these arise note that the menu doc would NOT be needed as the answer will lie elsewhere, outside of your scope;
RESERVATIONS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
Information on the reservation policies of the venue, this includes;
- Walk in customers seating policy.
- Minimum spends for reserved areas.
- Time limits on reservations.
- Cancellation policys (regarding late arrivals or no shows).
- How groups and large booking are handled.
Other detailed information includes;
- Detailed information on the seating layouts and descriptive information about the different parts of the venue which can be used to compare against the customers requested group size.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
UPCOMING EVENTS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information on the date, time, whether a ticket is needed, and a brief description of the event. Also rules and policies surrounding the specific events.
Any Information asking about upcoming events planned by the business should be referred onto the upcoming events document and thus exclude the venue information document.
MENU DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Pricing ,Ingredients and descriptions of all menu items.(It goes without saying availibility of menu items is not in the venue information document).
- This covers all food, drink and shisha related queries.
- Delivery availability of products, including services like Uber Eats or Foodpanda.
- Takeway of menu items policy.
- Customization of menu items.
- Special offers or happy hours.
- Last orders time for all menu items.
OPENING HOURS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- The 7 day regular working schedule of the venue. Is covered in the opening hours document.
- Last orders time and subsequent closing time for the kitchen, bar etc. Are covered in the opening hours document. Not the venue information document.
Any query that is answered by the opening hours document should not include the venue information document as it would be irrelevant context.
ALL OF THE QUERIES WHICH ARE DIRECTLY ANSWERABLE BY THE CORSSOVER TOPICS SHOULD NOT INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT.
### GUIDELINES ###
If a query asks about a "dining hall", a "theatre" or "bar" or anything that relates to a physical space. We will need the venue information to check if the venue has that space or not. We are not just including conntext to directly answer the querybut also to fact-check if the assumptions made in the query were correct.
Furthermore if the query mentions restrooms, or other facilities that are part of the physical space, the venue informationdocument should be included in the context regardless of the crux of the query.
EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY, IF IT MENTIONS A PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE, THE VENUE INFORMATION DOCUMENT SHOULD BE INCLUDED IN THE CONTEXT.
If a customer mentions wanting to do some form of activity at the venue, like reading a book, studying, working, or having a meeting. The venue information document should be included in the context. As the next node will need to know if the venue has the space to accomodate the customer's request but more importantly it give context on the interior style and ambiance and whether said activity is suitiable.
For example if a customer asks whether its possible to book a private event, the venue information is needed to provide a full a comprehensive answer. As if included, the next node will now be able to provide information on the venues spaces, ammenities and other parts of the physical space that would make it suitiable or not for a private event or custom booking.
The worst case scenario is a customer arrives for a booking but the venue cannot accomodate them due to a policy or physical constraint that was not considered in the response.
<｜Assistant｜>
<think>
Okay, let's see. The user is asking if they can store an unfinished drink for later in the evening.
First, I need to check if this falls under the venue information document. The guidelines say that the venue document covers rules on storing unfinished alcohol. The query is specifically about storing a drink, which aligns with that policy.
Next, I should check crossover topics. The menu document handles food and drink items but not policies on storing them. Reservations, events, and opening hours don't seem relevant here. The query isn't about reservations, events, or hours; it's about a policy.
Also, even though the query doesn't mention a physical space, the policy on storing drinks is explicitly part of the venue information. The guidelines state that if the answer is in the venue document, especially policies like this, we include it.
No mention of any crossover documents applies here. So the decision is to include the venue information document.
</think>
{
"reasoning": "The query is about the venue's policy regarding storing unfinished drinks, which is explicitly covered in the venue information document under 'Rules on storing unfinished alcohol for later consumption'. This does not fall under any crossover topics (reservations, events, menu, or opening hours) since it pertains directly to a specific facility-related policy. The venue information document is necessary to provide the correct answer regarding this policy.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the venue information document in the prompt is relevant for answering the user query. Ensure you take proper care and consideration to ensure you do not make the wrong decision.
To ensure you are able to make the correct decision, here is a breakdown of what is covered in the venue information document:
VENUE INFORMATION DOCUMENT CONTENTS:
- An abstract/blurb describing the venue.
- Information on location and accessability.
- Information on parking at the venue.
- Interior design and ambiance.
- The seating layout and capacity of the venue.
- The facilities and ammenities available at the venue(eg. wifi, ventillation system, sound system, projectors, restrooms facilites).
- All Information that is related to the physial space wil be in this document - this includes the dining area, bar, theatre, restrooms etc.
- Contact information for additional more complex queries.
- Service charges & all other additional charges.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Dress code.
- Minimum age restrictions.
- Minimum spend policy.
- Rules around patrons using their own decorations on reserved areas.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query is in one of the listed crossover topics, you exclude the document. The reasoning will be explained in the prompt.
The food and drink policy within the venue information document ONLY COVERS the rules and policies around bring in outside food and drinks. And storing unfinished alcohol. All food and drink policy outside of this can be considered crossover topics and will be handled in the menu document.
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude.
The venue information document does NOT have any information about the opening times of the venue. Queries about opening hours are thus a crossover topic and will be handled in the opening hours document.
ALL QUERIES THAT MENTION ANY PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE SHOULD INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT. EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in json format.
Ensure you follow the following json schema no matter the document or query you are working with:
EXAMPLE JSON OUTPUT:
{{
"reasoning": "This is where you explain your reasoning for the decision you made.",
"decision": "Will be either "include" or "exclude"."
}}
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I leave my unfinished drink here and pick it up next time?
### TASK ###
You are responsible for making a decision on whether the venue information document is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
### CROSSOVER TOPICS THAT ARE NOT IN THE VENUE INFORMATION DOCUMENT ###
ALL QUERIES HANDLED BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE VENUE INFORMATION DOCUMENT FROM THE CONTEXT.
If these arise note that the menu doc would NOT be needed as the answer will lie elsewhere, outside of your scope;
RESERVATIONS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
Information on the reservation policies of the venue, this includes;
- Walk in customers seating policy.
- Minimum spends for reserved areas.
- Time limits on reservations.
- Cancellation policys (regarding late arrivals or no shows).
- How groups and large booking are handled.
Other detailed information includes;
- Detailed information on the seating layouts and descriptive information about the different parts of the venue which can be used to compare against the customers requested group size.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
UPCOMING EVENTS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information on the date, time, whether a ticket is needed, and a brief description of the event. Also rules and policies surrounding the specific events.
Any Information asking about upcoming events planned by the business should be referred onto the upcoming events document and thus exclude the venue information document.
MENU DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Pricing ,Ingredients and descriptions of all menu items.(It goes without saying availibility of menu items is not in the venue information document).
- This covers all food, drink and shisha related queries.
- Delivery availability of products, including services like Uber Eats or Foodpanda.
- Takeway of menu items policy.
- Customization of menu items.
- Special offers or happy hours.
- Last orders time for all menu items.
OPENING HOURS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- The 7 day regular working schedule of the venue. Is covered in the opening hours document.
- Last orders time and subsequent closing time for the kitchen, bar etc. Are covered in the opening hours document. Not the venue information document.
Any query that is answered by the opening hours document should not include the venue information document as it would be irrelevant context.
ALL OF THE QUERIES WHICH ARE DIRECTLY ANSWERABLE BY THE CORSSOVER TOPICS SHOULD NOT INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT.
### GUIDELINES ###
If a query asks about a "dining hall", a "theatre" or "bar" or anything that relates to a physical space. We will need the venue information to check if the venue has that space or not. We are not just including conntext to directly answer the querybut also to fact-check if the assumptions made in the query were correct.
Furthermore if the query mentions restrooms, or other facilities that are part of the physical space, the venue informationdocument should be included in the context regardless of the crux of the query.
EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY, IF IT MENTIONS A PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE, THE VENUE INFORMATION DOCUMENT SHOULD BE INCLUDED IN THE CONTEXT.
If a customer mentions wanting to do some form of activity at the venue, like reading a book, studying, working, or having a meeting. The venue information document should be included in the context. As the next node will need to know if the venue has the space to accomodate the customer's request but more importantly it give context on the interior style and ambiance and whether said activity is suitiable.
For example if a customer asks whether its possible to book a private event, the venue information is needed to provide a full a comprehensive answer. As if included, the next node will now be able to provide information on the venues spaces, ammenities and other parts of the physical space that would make it suitiable or not for a private event or custom booking.
The worst case scenario is a customer arrives for a booking but the venue cannot accomodate them due to a policy or physical constraint that was not considered in the response.
<｜Assistant｜>
<think>
Okay, let's tackle this. The user is asking if they can leave their unfinished drink and pick it up next time. I need to check if the venue information document covers this.
From the contents listed, the venue information includes the policy on storing unfinished alcohol. The query is specifically about leaving a drink, which falls under that policy. Also, since the question involves a physical action at the venue (leaving something there), the venue document is relevant. No other documents like reservations or menu cover this. So the decision should be to include.
</think>
{
"reasoning": "The query asks about the policy for storing unfinished drinks for later pickup. According to the venue information document's contents, it covers 'Rules around storing unfinished alcohol for later consumption.' This directly addresses the user's question. Additionally, the query involves a physical action (leaving a drink at the venue), which relates to the venue's policies and facilities. No crossover topics (e.g., reservations, menu, events, or opening hours) are relevant here. Therefore, the venue information document is necessary to provide the correct policy details.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the venue information document in the prompt is relevant for answering the user query. Ensure you take proper care and consideration to ensure you do not make the wrong decision.
To ensure you are able to make the correct decision, here is a breakdown of what is covered in the venue information document:
VENUE INFORMATION DOCUMENT CONTENTS:
- An abstract/blurb describing the venue.
- Information on location and accessability.
- Information on parking at the venue.
- Interior design and ambiance.
- The seating layout and capacity of the venue.
- The facilities and ammenities available at the venue(eg. wifi, ventillation system, sound system, projectors, restrooms facilites).
- All Information that is related to the physial space wil be in this document - this includes the dining area, bar, theatre, restrooms etc.
- Contact information for additional more complex queries.
- Service charges & all other additional charges.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Dress code.
- Minimum age restrictions.
- Minimum spend policy.
- Rules around patrons using their own decorations on reserved areas.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query is in one of the listed crossover topics, you exclude the document. The reasoning will be explained in the prompt.
The food and drink policy within the venue information document ONLY COVERS the rules and policies around bring in outside food and drinks. And storing unfinished alcohol. All food and drink policy outside of this can be considered crossover topics and will be handled in the menu document.
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude.
The venue information document does NOT have any information about the opening times of the venue. Queries about opening hours are thus a crossover topic and will be handled in the opening hours document.
ALL QUERIES THAT MENTION ANY PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE SHOULD INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT. EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in json format.
Ensure you follow the following json schema no matter the document or query you are working with:
EXAMPLE JSON OUTPUT:
{{
"reasoning": "This is where you explain your reasoning for the decision you made.",
"decision": "Will be either "include" or "exclude"."
}}
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Is it possible to store my drink and come back for it on my next visit?
### TASK ###
You are responsible for making a decision on whether the venue information document is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
### CROSSOVER TOPICS THAT ARE NOT IN THE VENUE INFORMATION DOCUMENT ###
ALL QUERIES HANDLED BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE VENUE INFORMATION DOCUMENT FROM THE CONTEXT.
If these arise note that the menu doc would NOT be needed as the answer will lie elsewhere, outside of your scope;
RESERVATIONS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
Information on the reservation policies of the venue, this includes;
- Walk in customers seating policy.
- Minimum spends for reserved areas.
- Time limits on reservations.
- Cancellation policys (regarding late arrivals or no shows).
- How groups and large booking are handled.
Other detailed information includes;
- Detailed information on the seating layouts and descriptive information about the different parts of the venue which can be used to compare against the customers requested group size.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
UPCOMING EVENTS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information on the date, time, whether a ticket is needed, and a brief description of the event. Also rules and policies surrounding the specific events.
Any Information asking about upcoming events planned by the business should be referred onto the upcoming events document and thus exclude the venue information document.
MENU DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Pricing ,Ingredients and descriptions of all menu items.(It goes without saying availibility of menu items is not in the venue information document).
- This covers all food, drink and shisha related queries.
- Delivery availability of products, including services like Uber Eats or Foodpanda.
- Takeway of menu items policy.
- Customization of menu items.
- Special offers or happy hours.
- Last orders time for all menu items.
OPENING HOURS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- The 7 day regular working schedule of the venue. Is covered in the opening hours document.
- Last orders time and subsequent closing time for the kitchen, bar etc. Are covered in the opening hours document. Not the venue information document.
Any query that is answered by the opening hours document should not include the venue information document as it would be irrelevant context.
ALL OF THE QUERIES WHICH ARE DIRECTLY ANSWERABLE BY THE CORSSOVER TOPICS SHOULD NOT INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT.
### GUIDELINES ###
If a query asks about a "dining hall", a "theatre" or "bar" or anything that relates to a physical space. We will need the venue information to check if the venue has that space or not. We are not just including conntext to directly answer the querybut also to fact-check if the assumptions made in the query were correct.
Furthermore if the query mentions restrooms, or other facilities that are part of the physical space, the venue informationdocument should be included in the context regardless of the crux of the query.
EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY, IF IT MENTIONS A PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE, THE VENUE INFORMATION DOCUMENT SHOULD BE INCLUDED IN THE CONTEXT.
If a customer mentions wanting to do some form of activity at the venue, like reading a book, studying, working, or having a meeting. The venue information document should be included in the context. As the next node will need to know if the venue has the space to accomodate the customer's request but more importantly it give context on the interior style and ambiance and whether said activity is suitiable.
For example if a customer asks whether its possible to book a private event, the venue information is needed to provide a full a comprehensive answer. As if included, the next node will now be able to provide information on the venues spaces, ammenities and other parts of the physical space that would make it suitiable or not for a private event or custom booking.
The worst case scenario is a customer arrives for a booking but the venue cannot accomodate them due to a policy or physical constraint that was not considered in the response.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking if they can store their drink and come back for it on their next visit. First, I need to check what the venue information document covers. From the guidelines, the venue info includes rules on storing unfinished alcohol. That's directly related to the query. Even though the query is about a drink, which might seem like a menu item, the policy on storage is part of the venue's rules. The menu document handles food and drink items themselves, delivery, customization, etc., but not storage policies. Also, the query doesn't mention any crossover topics like reservations, events, opening hours, or menu specifics. Since the storage policy is explicitly covered in the venue info, the answer should be there. So, include the venue document.
</think>
{
"reasoning": "The query asks about the policy of storing a drink for later consumption, which is explicitly covered in the venue information document under 'Rules on storing unfinished alcohol for later consumption.' This policy pertains to the venue's specific rules and does not fall under crossover topics like menu items, reservations, events, or opening hours. Therefore, the venue information document is relevant to answer this query.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the venue information document in the prompt is relevant for answering the user query. Ensure you take proper care and consideration to ensure you do not make the wrong decision.
To ensure you are able to make the correct decision, here is a breakdown of what is covered in the venue information document:
VENUE INFORMATION DOCUMENT CONTENTS:
- An abstract/blurb describing the venue.
- Information on location and accessability.
- Information on parking at the venue.
- Interior design and ambiance.
- The seating layout and capacity of the venue.
- The facilities and ammenities available at the venue(eg. wifi, ventillation system, sound system, projectors, restrooms facilites).
- All Information that is related to the physial space wil be in this document - this includes the dining area, bar, theatre, restrooms etc.
- Contact information for additional more complex queries.
- Service charges & all other additional charges.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Dress code.
- Minimum age restrictions.
- Minimum spend policy.
- Rules around patrons using their own decorations on reserved areas.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query is in one of the listed crossover topics, you exclude the document. The reasoning will be explained in the prompt.
The food and drink policy within the venue information document ONLY COVERS the rules and policies around bring in outside food and drinks. And storing unfinished alcohol. All food and drink policy outside of this can be considered crossover topics and will be handled in the menu document.
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude.
The venue information document does NOT have any information about the opening times of the venue. Queries about opening hours are thus a crossover topic and will be handled in the opening hours document.
ALL QUERIES THAT MENTION ANY PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE SHOULD INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT. EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in json format.
Ensure you follow the following json schema no matter the document or query you are working with:
EXAMPLE JSON OUTPUT:
{{
"reasoning": "This is where you explain your reasoning for the decision you made.",
"decision": "Will be either "include" or "exclude"."
}}
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I leave my drink and have it saved for me to finish later, when I return?
### TASK ###
You are responsible for making a decision on whether the venue information document is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
### CROSSOVER TOPICS THAT ARE NOT IN THE VENUE INFORMATION DOCUMENT ###
ALL QUERIES HANDLED BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE VENUE INFORMATION DOCUMENT FROM THE CONTEXT.
If these arise note that the menu doc would NOT be needed as the answer will lie elsewhere, outside of your scope;
RESERVATIONS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
Information on the reservation policies of the venue, this includes;
- Walk in customers seating policy.
- Minimum spends for reserved areas.
- Time limits on reservations.
- Cancellation policys (regarding late arrivals or no shows).
- How groups and large booking are handled.
Other detailed information includes;
- Detailed information on the seating layouts and descriptive information about the different parts of the venue which can be used to compare against the customers requested group size.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
UPCOMING EVENTS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information on the date, time, whether a ticket is needed, and a brief description of the event. Also rules and policies surrounding the specific events.
Any Information asking about upcoming events planned by the business should be referred onto the upcoming events document and thus exclude the venue information document.
MENU DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Pricing ,Ingredients and descriptions of all menu items.(It goes without saying availibility of menu items is not in the venue information document).
- This covers all food, drink and shisha related queries.
- Delivery availability of products, including services like Uber Eats or Foodpanda.
- Takeway of menu items policy.
- Customization of menu items.
- Special offers or happy hours.
- Last orders time for all menu items.
OPENING HOURS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- The 7 day regular working schedule of the venue. Is covered in the opening hours document.
- Last orders time and subsequent closing time for the kitchen, bar etc. Are covered in the opening hours document. Not the venue information document.
Any query that is answered by the opening hours document should not include the venue information document as it would be irrelevant context.
ALL OF THE QUERIES WHICH ARE DIRECTLY ANSWERABLE BY THE CORSSOVER TOPICS SHOULD NOT INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT.
### GUIDELINES ###
If a query asks about a "dining hall", a "theatre" or "bar" or anything that relates to a physical space. We will need the venue information to check if the venue has that space or not. We are not just including conntext to directly answer the querybut also to fact-check if the assumptions made in the query were correct.
Furthermore if the query mentions restrooms, or other facilities that are part of the physical space, the venue informationdocument should be included in the context regardless of the crux of the query.
EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY, IF IT MENTIONS A PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE, THE VENUE INFORMATION DOCUMENT SHOULD BE INCLUDED IN THE CONTEXT.
If a customer mentions wanting to do some form of activity at the venue, like reading a book, studying, working, or having a meeting. The venue information document should be included in the context. As the next node will need to know if the venue has the space to accomodate the customer's request but more importantly it give context on the interior style and ambiance and whether said activity is suitiable.
For example if a customer asks whether its possible to book a private event, the venue information is needed to provide a full a comprehensive answer. As if included, the next node will now be able to provide information on the venues spaces, ammenities and other parts of the physical space that would make it suitiable or not for a private event or custom booking.
The worst case scenario is a customer arrives for a booking but the venue cannot accomodate them due to a policy or physical constraint that was not considered in the response.
<｜Assistant｜>
<think>
Okay, let's tackle this query. The user is asking, "Can I leave my drink and have it saved for me to finish later, when I return?"
First, I need to check the contents of the venue information document. According to the guidelines, the venue information covers policies on storing unfinished alcohol. The user is specifically asking about saving a drink for later, which falls under that policy.
The crossover topics mention that food and drink policies outside of bringing in outside items or storing alcohol are handled elsewhere, but here the query is directly about storing an unfinished drink. Therefore, the venue document should include this information.
Also, even though the query doesn't mention a physical space, the policy itself is part of the venue's rules, which are documented in the venue information. The guidelines state that rules on storing unfinished alcohol are included here. There's no mention of reservations, events, menu items, or opening hours, so those crossover documents aren't relevant here.
So, the decision is to include the venue information document because it directly addresses the policy in question.
</think>
{
"reasoning": "The query asks about saving a drink for later consumption, which directly relates to the venue's policy on storing unfinished alcohol. According to the venue information document's contents, rules around storing unfinished alcohol are explicitly covered. There is no overlap with crossover topics (e.g., reservations, events, menu items, or opening hours). The mention of a physical action (leaving a drink) does not require inclusion of physical space details but aligns with the documented food/drink storage policy.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the venue information document in the prompt is relevant for answering the user query. Ensure you take proper care and consideration to ensure you do not make the wrong decision.
To ensure you are able to make the correct decision, here is a breakdown of what is covered in the venue information document:
VENUE INFORMATION DOCUMENT CONTENTS:
- An abstract/blurb describing the venue.
- Information on location and accessability.
- Information on parking at the venue.
- Interior design and ambiance.
- The seating layout and capacity of the venue.
- The facilities and ammenities available at the venue(eg. wifi, ventillation system, sound system, projectors, restrooms facilites).
- All Information that is related to the physial space wil be in this document - this includes the dining area, bar, theatre, restrooms etc.
- Contact information for additional more complex queries.
- Service charges & all other additional charges.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Dress code.
- Minimum age restrictions.
- Minimum spend policy.
- Rules around patrons using their own decorations on reserved areas.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query is in one of the listed crossover topics, you exclude the document. The reasoning will be explained in the prompt.
The food and drink policy within the venue information document ONLY COVERS the rules and policies around bring in outside food and drinks. And storing unfinished alcohol. All food and drink policy outside of this can be considered crossover topics and will be handled in the menu document.
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude.
The venue information document does NOT have any information about the opening times of the venue. Queries about opening hours are thus a crossover topic and will be handled in the opening hours document.
ALL QUERIES THAT MENTION ANY PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE SHOULD INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT. EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in json format.
Ensure you follow the following json schema no matter the document or query you are working with:
EXAMPLE JSON OUTPUT:
{{
"reasoning": "This is where you explain your reasoning for the decision you made.",
"decision": "Will be either "include" or "exclude"."
}}
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Would it be alright if I store my unfinished drink and come back for it next time?
### TASK ###
You are responsible for making a decision on whether the venue information document is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
### CROSSOVER TOPICS THAT ARE NOT IN THE VENUE INFORMATION DOCUMENT ###
ALL QUERIES HANDLED BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE VENUE INFORMATION DOCUMENT FROM THE CONTEXT.
If these arise note that the menu doc would NOT be needed as the answer will lie elsewhere, outside of your scope;
RESERVATIONS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
Information on the reservation policies of the venue, this includes;
- Walk in customers seating policy.
- Minimum spends for reserved areas.
- Time limits on reservations.
- Cancellation policys (regarding late arrivals or no shows).
- How groups and large booking are handled.
Other detailed information includes;
- Detailed information on the seating layouts and descriptive information about the different parts of the venue which can be used to compare against the customers requested group size.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
UPCOMING EVENTS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information on the date, time, whether a ticket is needed, and a brief description of the event. Also rules and policies surrounding the specific events.
Any Information asking about upcoming events planned by the business should be referred onto the upcoming events document and thus exclude the venue information document.
MENU DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Pricing ,Ingredients and descriptions of all menu items.(It goes without saying availibility of menu items is not in the venue information document).
- This covers all food, drink and shisha related queries.
- Delivery availability of products, including services like Uber Eats or Foodpanda.
- Takeway of menu items policy.
- Customization of menu items.
- Special offers or happy hours.
- Last orders time for all menu items.
OPENING HOURS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- The 7 day regular working schedule of the venue. Is covered in the opening hours document.
- Last orders time and subsequent closing time for the kitchen, bar etc. Are covered in the opening hours document. Not the venue information document.
Any query that is answered by the opening hours document should not include the venue information document as it would be irrelevant context.
ALL OF THE QUERIES WHICH ARE DIRECTLY ANSWERABLE BY THE CORSSOVER TOPICS SHOULD NOT INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT.
### GUIDELINES ###
If a query asks about a "dining hall", a "theatre" or "bar" or anything that relates to a physical space. We will need the venue information to check if the venue has that space or not. We are not just including conntext to directly answer the querybut also to fact-check if the assumptions made in the query were correct.
Furthermore if the query mentions restrooms, or other facilities that are part of the physical space, the venue informationdocument should be included in the context regardless of the crux of the query.
EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY, IF IT MENTIONS A PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE, THE VENUE INFORMATION DOCUMENT SHOULD BE INCLUDED IN THE CONTEXT.
If a customer mentions wanting to do some form of activity at the venue, like reading a book, studying, working, or having a meeting. The venue information document should be included in the context. As the next node will need to know if the venue has the space to accomodate the customer's request but more importantly it give context on the interior style and ambiance and whether said activity is suitiable.
For example if a customer asks whether its possible to book a private event, the venue information is needed to provide a full a comprehensive answer. As if included, the next node will now be able to provide information on the venues spaces, ammenities and other parts of the physical space that would make it suitiable or not for a private event or custom booking.
The worst case scenario is a customer arrives for a booking but the venue cannot accomodate them due to a policy or physical constraint that was not considered in the response.
<｜Assistant｜>
<think>
Alright, let's tackle this query. The user is asking if they can store their unfinished drink and come back for it next time.
First, I need to check which document this falls under. The venue information document covers rules around storing unfinished alcohol. According to the guidelines, food and drink policies related to bringing in outside items or storing leftovers are part of the venue info.
The query specifically mentions storing a drink, which is directly addressed in the venue document's policies. Even though the user mentions coming back later, which might touch on reservations or opening hours, the core of the question is about the storage policy.
Also, the guidelines state that any mention of physical facilities (like storage for drinks) requires including the venue document. Since there's no crossover with reservations, menu, or events here, the decision is to include the venue info.
</think>
{
"reasoning": "The query asks about storing an unfinished drink for later consumption, which is explicitly covered in the venue information document under 'Rules on storing unfinished alcohol for later consumption'. This policy is part of the venue's operational rules and does not fall under crossover topics like reservations, menu, or events. Therefore, the venue information document is necessary to answer the query accurately.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the venue information document in the prompt is relevant for answering the user query. Ensure you take proper care and consideration to ensure you do not make the wrong decision.
To ensure you are able to make the correct decision, here is a breakdown of what is covered in the venue information document:
VENUE INFORMATION DOCUMENT CONTENTS:
- An abstract/blurb describing the venue.
- Information on location and accessability.
- Information on parking at the venue.
- Interior design and ambiance.
- The seating layout and capacity of the venue.
- The facilities and ammenities available at the venue(eg. wifi, ventillation system, sound system, projectors, restrooms facilites).
- All Information that is related to the physial space wil be in this document - this includes the dining area, bar, theatre, restrooms etc.
- Contact information for additional more complex queries.
- Service charges & all other additional charges.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Dress code.
- Minimum age restrictions.
- Minimum spend policy.
- Rules around patrons using their own decorations on reserved areas.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query is in one of the listed crossover topics, you exclude the document. The reasoning will be explained in the prompt.
The food and drink policy within the venue information document ONLY COVERS the rules and policies around bring in outside food and drinks. And storing unfinished alcohol. All food and drink policy outside of this can be considered crossover topics and will be handled in the menu document.
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude.
The venue information document does NOT have any information about the opening times of the venue. Queries about opening hours are thus a crossover topic and will be handled in the opening hours document.
ALL QUERIES THAT MENTION ANY PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE SHOULD INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT. EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in json format.
Ensure you follow the following json schema no matter the document or query you are working with:
EXAMPLE JSON OUTPUT:
{{
"reasoning": "This is where you explain your reasoning for the decision you made.",
"decision": "Will be either "include" or "exclude"."
}}
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Can you keep my drink for me until I return next week?
### TASK ###
You are responsible for making a decision on whether the venue information document is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
### CROSSOVER TOPICS THAT ARE NOT IN THE VENUE INFORMATION DOCUMENT ###
ALL QUERIES HANDLED BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE VENUE INFORMATION DOCUMENT FROM THE CONTEXT.
If these arise note that the menu doc would NOT be needed as the answer will lie elsewhere, outside of your scope;
RESERVATIONS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
Information on the reservation policies of the venue, this includes;
- Walk in customers seating policy.
- Minimum spends for reserved areas.
- Time limits on reservations.
- Cancellation policys (regarding late arrivals or no shows).
- How groups and large booking are handled.
Other detailed information includes;
- Detailed information on the seating layouts and descriptive information about the different parts of the venue which can be used to compare against the customers requested group size.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
UPCOMING EVENTS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information on the date, time, whether a ticket is needed, and a brief description of the event. Also rules and policies surrounding the specific events.
Any Information asking about upcoming events planned by the business should be referred onto the upcoming events document and thus exclude the venue information document.
MENU DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Pricing ,Ingredients and descriptions of all menu items.(It goes without saying availibility of menu items is not in the venue information document).
- This covers all food, drink and shisha related queries.
- Delivery availability of products, including services like Uber Eats or Foodpanda.
- Takeway of menu items policy.
- Customization of menu items.
- Special offers or happy hours.
- Last orders time for all menu items.
OPENING HOURS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- The 7 day regular working schedule of the venue. Is covered in the opening hours document.
- Last orders time and subsequent closing time for the kitchen, bar etc. Are covered in the opening hours document. Not the venue information document.
Any query that is answered by the opening hours document should not include the venue information document as it would be irrelevant context.
ALL OF THE QUERIES WHICH ARE DIRECTLY ANSWERABLE BY THE CORSSOVER TOPICS SHOULD NOT INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT.
### GUIDELINES ###
If a query asks about a "dining hall", a "theatre" or "bar" or anything that relates to a physical space. We will need the venue information to check if the venue has that space or not. We are not just including conntext to directly answer the querybut also to fact-check if the assumptions made in the query were correct.
Furthermore if the query mentions restrooms, or other facilities that are part of the physical space, the venue informationdocument should be included in the context regardless of the crux of the query.
EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY, IF IT MENTIONS A PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE, THE VENUE INFORMATION DOCUMENT SHOULD BE INCLUDED IN THE CONTEXT.
If a customer mentions wanting to do some form of activity at the venue, like reading a book, studying, working, or having a meeting. The venue information document should be included in the context. As the next node will need to know if the venue has the space to accomodate the customer's request but more importantly it give context on the interior style and ambiance and whether said activity is suitiable.
For example if a customer asks whether its possible to book a private event, the venue information is needed to provide a full a comprehensive answer. As if included, the next node will now be able to provide information on the venues spaces, ammenities and other parts of the physical space that would make it suitiable or not for a private event or custom booking.
The worst case scenario is a customer arrives for a booking but the venue cannot accomodate them due to a policy or physical constraint that was not considered in the response.
<｜Assistant｜>
<think>
Okay, let's try to figure out whether to include the venue information document for the query "Can you keep my drink for me until I return next week?"
First, the user is asking about storing a drink until they come back next week. From the venue info document content, there's a section on rules around storing unfinished alcohol. The document mentions policies on keeping unfinished alcohol for later. Even though the query doesn't specify alcohol, storing any drink would fall under the venue's policies on handling such requests.
Looking at the crossover topics, the query isn't about reservations, events, menu items, or opening hours. The main point is about the venue's policy on storing drinks, which is covered in the venue information document. Also, the guidelines state that any mention of policies related to the venue's rules (like storing drinks) should include the document.
Additionally, even if the query doesn't mention a physical space, the policy itself is part of the venue's rules, which are documented there. There's no overlap with other documents here, so the decision should be to include the venue information.
</think>
{
"reasoning": "The query asks whether the venue can keep a drink until the customer returns next week. The venue information document includes rules on storing unfinished alcohol for later consumption, which directly addresses policies related to holding beverages. Although the query does not explicitly mention a physical space, the policy itself is part of the venue's operational rules covered in the document. Additionally, the decision to include aligns with the guideline that venue policies (e.g., storage of drinks) are within the scope of the venue information document. There is no crossover to other documents like reservations, menu, or opening hours here.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the venue information document in the prompt is relevant for answering the user query. Ensure you take proper care and consideration to ensure you do not make the wrong decision.
To ensure you are able to make the correct decision, here is a breakdown of what is covered in the venue information document:
VENUE INFORMATION DOCUMENT CONTENTS:
- An abstract/blurb describing the venue.
- Information on location and accessability.
- Information on parking at the venue.
- Interior design and ambiance.
- The seating layout and capacity of the venue.
- The facilities and ammenities available at the venue(eg. wifi, ventillation system, sound system, projectors, restrooms facilites).
- All Information that is related to the physial space wil be in this document - this includes the dining area, bar, theatre, restrooms etc.
- Contact information for additional more complex queries.
- Service charges & all other additional charges.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Dress code.
- Minimum age restrictions.
- Minimum spend policy.
- Rules around patrons using their own decorations on reserved areas.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query is in one of the listed crossover topics, you exclude the document. The reasoning will be explained in the prompt.
The food and drink policy within the venue information document ONLY COVERS the rules and policies around bring in outside food and drinks. And storing unfinished alcohol. All food and drink policy outside of this can be considered crossover topics and will be handled in the menu document.
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude.
The venue information document does NOT have any information about the opening times of the venue. Queries about opening hours are thus a crossover topic and will be handled in the opening hours document.
ALL QUERIES THAT MENTION ANY PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE SHOULD INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT. EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in json format.
Ensure you follow the following json schema no matter the document or query you are working with:
EXAMPLE JSON OUTPUT:
{{
"reasoning": "This is where you explain your reasoning for the decision you made.",
"decision": "Will be either "include" or "exclude"."
}}
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Is there a way to store my drink and have it ready for me when I come back?
### TASK ###
You are responsible for making a decision on whether the venue information document is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
### CROSSOVER TOPICS THAT ARE NOT IN THE VENUE INFORMATION DOCUMENT ###
ALL QUERIES HANDLED BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE VENUE INFORMATION DOCUMENT FROM THE CONTEXT.
If these arise note that the menu doc would NOT be needed as the answer will lie elsewhere, outside of your scope;
RESERVATIONS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
Information on the reservation policies of the venue, this includes;
- Walk in customers seating policy.
- Minimum spends for reserved areas.
- Time limits on reservations.
- Cancellation policys (regarding late arrivals or no shows).
- How groups and large booking are handled.
Other detailed information includes;
- Detailed information on the seating layouts and descriptive information about the different parts of the venue which can be used to compare against the customers requested group size.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
UPCOMING EVENTS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information on the date, time, whether a ticket is needed, and a brief description of the event. Also rules and policies surrounding the specific events.
Any Information asking about upcoming events planned by the business should be referred onto the upcoming events document and thus exclude the venue information document.
MENU DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Pricing ,Ingredients and descriptions of all menu items.(It goes without saying availibility of menu items is not in the venue information document).
- This covers all food, drink and shisha related queries.
- Delivery availability of products, including services like Uber Eats or Foodpanda.
- Takeway of menu items policy.
- Customization of menu items.
- Special offers or happy hours.
- Last orders time for all menu items.
OPENING HOURS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- The 7 day regular working schedule of the venue. Is covered in the opening hours document.
- Last orders time and subsequent closing time for the kitchen, bar etc. Are covered in the opening hours document. Not the venue information document.
Any query that is answered by the opening hours document should not include the venue information document as it would be irrelevant context.
ALL OF THE QUERIES WHICH ARE DIRECTLY ANSWERABLE BY THE CORSSOVER TOPICS SHOULD NOT INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT.
### GUIDELINES ###
If a query asks about a "dining hall", a "theatre" or "bar" or anything that relates to a physical space. We will need the venue information to check if the venue has that space or not. We are not just including conntext to directly answer the querybut also to fact-check if the assumptions made in the query were correct.
Furthermore if the query mentions restrooms, or other facilities that are part of the physical space, the venue informationdocument should be included in the context regardless of the crux of the query.
EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY, IF IT MENTIONS A PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE, THE VENUE INFORMATION DOCUMENT SHOULD BE INCLUDED IN THE CONTEXT.
If a customer mentions wanting to do some form of activity at the venue, like reading a book, studying, working, or having a meeting. The venue information document should be included in the context. As the next node will need to know if the venue has the space to accomodate the customer's request but more importantly it give context on the interior style and ambiance and whether said activity is suitiable.
For example if a customer asks whether its possible to book a private event, the venue information is needed to provide a full a comprehensive answer. As if included, the next node will now be able to provide information on the venues spaces, ammenities and other parts of the physical space that would make it suitiable or not for a private event or custom booking.
The worst case scenario is a customer arrives for a booking but the venue cannot accomodate them due to a policy or physical constraint that was not considered in the response.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking if they can store their drink and have it ready when they return. According to the guidelines, the venue information document covers policies on storing unfinished alcohol. The query specifically mentions storing a drink, which falls under this policy. Also, even though it's about a drink, the main issue here is the venue's policy on storage, not the drink itself. Since the venue document includes rules about storing alcohol, this query is directly addressed there. There's no mention of reservations, events, menu items, or opening hours, so no crossover topics. Plus, the query involves a facility-related policy, which the guidelines say should include the venue document.
I need to check if any crossover topics apply. The query isn't about reservations, events, menu items, or opening hours. It's about a policy related to handling drinks post-purchase, which the venue info covers. Therefore, the decision should be to include the venue information document.
</think>
{
"reasoning": "The query asks about storing a drink for later, which directly relates to the venue's policy on storing unfinished alcohol. The venue information document explicitly covers rules and policies around storing unfinished alcohol, making it relevant. Additionally, the query involves a facility-related policy (handling of drinks), which according to the guidelines requires including the venue information document even if other aspects are involved. No crossover topics (reservations, events, menu, or opening hours) are implicated here.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the venue information document in the prompt is relevant for answering the user query. Ensure you take proper care and consideration to ensure you do not make the wrong decision.
To ensure you are able to make the correct decision, here is a breakdown of what is covered in the venue information document:
VENUE INFORMATION DOCUMENT CONTENTS:
- An abstract/blurb describing the venue.
- Information on location and accessability.
- Information on parking at the venue.
- Interior design and ambiance.
- The seating layout and capacity of the venue.
- The facilities and ammenities available at the venue(eg. wifi, ventillation system, sound system, projectors, restrooms facilites).
- All Information that is related to the physial space wil be in this document - this includes the dining area, bar, theatre, restrooms etc.
- Contact information for additional more complex queries.
- Service charges & all other additional charges.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Dress code.
- Minimum age restrictions.
- Minimum spend policy.
- Rules around patrons using their own decorations on reserved areas.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query is in one of the listed crossover topics, you exclude the document. The reasoning will be explained in the prompt.
The food and drink policy within the venue information document ONLY COVERS the rules and policies around bring in outside food and drinks. And storing unfinished alcohol. All food and drink policy outside of this can be considered crossover topics and will be handled in the menu document.
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude.
The venue information document does NOT have any information about the opening times of the venue. Queries about opening hours are thus a crossover topic and will be handled in the opening hours document.
ALL QUERIES THAT MENTION ANY PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE SHOULD INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT. EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in json format.
Ensure you follow the following json schema no matter the document or query you are working with:
EXAMPLE JSON OUTPUT:
{{
"reasoning": "This is where you explain your reasoning for the decision you made.",
"decision": "Will be either "include" or "exclude"."
}}
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I leave my drink here to finish when I come back next time?
### TASK ###
You are responsible for making a decision on whether the venue information document is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
### CROSSOVER TOPICS THAT ARE NOT IN THE VENUE INFORMATION DOCUMENT ###
ALL QUERIES HANDLED BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE VENUE INFORMATION DOCUMENT FROM THE CONTEXT.
If these arise note that the menu doc would NOT be needed as the answer will lie elsewhere, outside of your scope;
RESERVATIONS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
Information on the reservation policies of the venue, this includes;
- Walk in customers seating policy.
- Minimum spends for reserved areas.
- Time limits on reservations.
- Cancellation policys (regarding late arrivals or no shows).
- How groups and large booking are handled.
Other detailed information includes;
- Detailed information on the seating layouts and descriptive information about the different parts of the venue which can be used to compare against the customers requested group size.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
UPCOMING EVENTS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information on the date, time, whether a ticket is needed, and a brief description of the event. Also rules and policies surrounding the specific events.
Any Information asking about upcoming events planned by the business should be referred onto the upcoming events document and thus exclude the venue information document.
MENU DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Pricing ,Ingredients and descriptions of all menu items.(It goes without saying availibility of menu items is not in the venue information document).
- This covers all food, drink and shisha related queries.
- Delivery availability of products, including services like Uber Eats or Foodpanda.
- Takeway of menu items policy.
- Customization of menu items.
- Special offers or happy hours.
- Last orders time for all menu items.
OPENING HOURS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- The 7 day regular working schedule of the venue. Is covered in the opening hours document.
- Last orders time and subsequent closing time for the kitchen, bar etc. Are covered in the opening hours document. Not the venue information document.
Any query that is answered by the opening hours document should not include the venue information document as it would be irrelevant context.
ALL OF THE QUERIES WHICH ARE DIRECTLY ANSWERABLE BY THE CORSSOVER TOPICS SHOULD NOT INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT.
### GUIDELINES ###
If a query asks about a "dining hall", a "theatre" or "bar" or anything that relates to a physical space. We will need the venue information to check if the venue has that space or not. We are not just including conntext to directly answer the querybut also to fact-check if the assumptions made in the query were correct.
Furthermore if the query mentions restrooms, or other facilities that are part of the physical space, the venue informationdocument should be included in the context regardless of the crux of the query.
EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY, IF IT MENTIONS A PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE, THE VENUE INFORMATION DOCUMENT SHOULD BE INCLUDED IN THE CONTEXT.
If a customer mentions wanting to do some form of activity at the venue, like reading a book, studying, working, or having a meeting. The venue information document should be included in the context. As the next node will need to know if the venue has the space to accomodate the customer's request but more importantly it give context on the interior style and ambiance and whether said activity is suitiable.
For example if a customer asks whether its possible to book a private event, the venue information is needed to provide a full a comprehensive answer. As if included, the next node will now be able to provide information on the venues spaces, ammenities and other parts of the physical space that would make it suitiable or not for a private event or custom booking.
The worst case scenario is a customer arrives for a booking but the venue cannot accomodate them due to a policy or physical constraint that was not considered in the response.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking if they can leave their drink to finish next time they come back. From the guidelines, the venue information document includes policies on storing unfinished alcohol. The query is about storing a drink for later, which directly relates to the venue's policy on this matter. Also, even though the main point is the policy, mentioning the act of leaving a drink involves the physical space (like where it's stored), so by the guidelines, that's another reason to include the document. There's no mention of reservations, events, menu items, or opening hours here, so none of the crossover topics apply. Therefore, the decision is to include the venue information document.
</think>
{
"reasoning": "The user is asking about leaving their drink at the venue to finish later, which directly relates to the venue's policy on storing unfinished alcohol. The venue information document explicitly covers rules around storing unfinished alcohol, making it necessary to include this document in the context. Additionally, the query implicitly involves the physical space of the venue (e.g., storage facilities or policies tied to the venue's operations). Even though the query does not explicitly mention a physical space, the act of leaving a drink involves the venue's policies and storage logistics, which are documented in the venue information document. There are no crossover topics (e.g., reservations, events, menu, or opening hours) that would override the need for this document.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the venue information document in the prompt is relevant for answering the user query. Ensure you take proper care and consideration to ensure you do not make the wrong decision.
To ensure you are able to make the correct decision, here is a breakdown of what is covered in the venue information document:
VENUE INFORMATION DOCUMENT CONTENTS:
- An abstract/blurb describing the venue.
- Information on location and accessability.
- Information on parking at the venue.
- Interior design and ambiance.
- The seating layout and capacity of the venue.
- The facilities and ammenities available at the venue(eg. wifi, ventillation system, sound system, projectors, restrooms facilites).
- All Information that is related to the physial space wil be in this document - this includes the dining area, bar, theatre, restrooms etc.
- Contact information for additional more complex queries.
- Service charges & all other additional charges.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Dress code.
- Minimum age restrictions.
- Minimum spend policy.
- Rules around patrons using their own decorations on reserved areas.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query is in one of the listed crossover topics, you exclude the document. The reasoning will be explained in the prompt.
The food and drink policy within the venue information document ONLY COVERS the rules and policies around bring in outside food and drinks. And storing unfinished alcohol. All food and drink policy outside of this can be considered crossover topics and will be handled in the menu document.
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude.
The venue information document does NOT have any information about the opening times of the venue. Queries about opening hours are thus a crossover topic and will be handled in the opening hours document.
ALL QUERIES THAT MENTION ANY PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE SHOULD INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT. EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in json format.
Ensure you follow the following json schema no matter the document or query you are working with:
EXAMPLE JSON OUTPUT:
{{
"reasoning": "This is where you explain your reasoning for the decision you made.",
"decision": "Will be either "include" or "exclude"."
}}
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Is it okay to store my unfinished drink for the next time I visit?
### TASK ###
You are responsible for making a decision on whether the venue information document is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
### CROSSOVER TOPICS THAT ARE NOT IN THE VENUE INFORMATION DOCUMENT ###
ALL QUERIES HANDLED BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE VENUE INFORMATION DOCUMENT FROM THE CONTEXT.
If these arise note that the menu doc would NOT be needed as the answer will lie elsewhere, outside of your scope;
RESERVATIONS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
Information on the reservation policies of the venue, this includes;
- Walk in customers seating policy.
- Minimum spends for reserved areas.
- Time limits on reservations.
- Cancellation policys (regarding late arrivals or no shows).
- How groups and large booking are handled.
Other detailed information includes;
- Detailed information on the seating layouts and descriptive information about the different parts of the venue which can be used to compare against the customers requested group size.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
UPCOMING EVENTS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information on the date, time, whether a ticket is needed, and a brief description of the event. Also rules and policies surrounding the specific events.
Any Information asking about upcoming events planned by the business should be referred onto the upcoming events document and thus exclude the venue information document.
MENU DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Pricing ,Ingredients and descriptions of all menu items.(It goes without saying availibility of menu items is not in the venue information document).
- This covers all food, drink and shisha related queries.
- Delivery availability of products, including services like Uber Eats or Foodpanda.
- Takeway of menu items policy.
- Customization of menu items.
- Special offers or happy hours.
- Last orders time for all menu items.
OPENING HOURS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- The 7 day regular working schedule of the venue. Is covered in the opening hours document.
- Last orders time and subsequent closing time for the kitchen, bar etc. Are covered in the opening hours document. Not the venue information document.
Any query that is answered by the opening hours document should not include the venue information document as it would be irrelevant context.
ALL OF THE QUERIES WHICH ARE DIRECTLY ANSWERABLE BY THE CORSSOVER TOPICS SHOULD NOT INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT.
### GUIDELINES ###
If a query asks about a "dining hall", a "theatre" or "bar" or anything that relates to a physical space. We will need the venue information to check if the venue has that space or not. We are not just including conntext to directly answer the querybut also to fact-check if the assumptions made in the query were correct.
Furthermore if the query mentions restrooms, or other facilities that are part of the physical space, the venue informationdocument should be included in the context regardless of the crux of the query.
EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY, IF IT MENTIONS A PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE, THE VENUE INFORMATION DOCUMENT SHOULD BE INCLUDED IN THE CONTEXT.
If a customer mentions wanting to do some form of activity at the venue, like reading a book, studying, working, or having a meeting. The venue information document should be included in the context. As the next node will need to know if the venue has the space to accomodate the customer's request but more importantly it give context on the interior style and ambiance and whether said activity is suitiable.
For example if a customer asks whether its possible to book a private event, the venue information is needed to provide a full a comprehensive answer. As if included, the next node will now be able to provide information on the venues spaces, ammenities and other parts of the physical space that would make it suitiable or not for a private event or custom booking.
The worst case scenario is a customer arrives for a booking but the venue cannot accomodate them due to a policy or physical constraint that was not considered in the response.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking if they can store their unfinished drink for their next visit. I need to check if the venue information document has the answer.
From the guidelines, the venue info covers rules on storing unfinished alcohol. The query is specifically about storing a drink, which falls under that policy. The menu document handles product-related stuff, but this is a policy, not about the drink itself.
Also, even though the main point is the policy, since it's about the venue's rules, the venue info is relevant. The crossover topics like reservations or events don't apply here. There's no mention of physical spaces here, but the policy itself is part of the venue's rules. So, include the venue info to answer the storage policy accurately.
</think>
{
"reasoning": "The query asks about the policy on storing unfinished drinks for a future visit. According to the venue information document's contents, it covers 'rules around storing unfinished alcohol for later consumption.' This directly addresses the user's question. The query does not relate to menu items, reservations, upcoming events, or opening hours, which are handled by other documents. Since the venue information document explicitly includes policies on this matter, it is necessary to include it in the context for an accurate response.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the venue information document in the prompt is relevant for answering the user query. Ensure you take proper care and consideration to ensure you do not make the wrong decision.
To ensure you are able to make the correct decision, here is a breakdown of what is covered in the venue information document:
VENUE INFORMATION DOCUMENT CONTENTS:
- An abstract/blurb describing the venue.
- Information on location and accessability.
- Information on parking at the venue.
- Interior design and ambiance.
- The seating layout and capacity of the venue.
- The facilities and ammenities available at the venue(eg. wifi, ventillation system, sound system, projectors, restrooms facilites).
- All Information that is related to the physial space wil be in this document - this includes the dining area, bar, theatre, restrooms etc.
- Contact information for additional more complex queries.
- Service charges & all other additional charges.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Dress code.
- Minimum age restrictions.
- Minimum spend policy.
- Rules around patrons using their own decorations on reserved areas.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query is in one of the listed crossover topics, you exclude the document. The reasoning will be explained in the prompt.
The food and drink policy within the venue information document ONLY COVERS the rules and policies around bring in outside food and drinks. And storing unfinished alcohol. All food and drink policy outside of this can be considered crossover topics and will be handled in the menu document.
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude.
The venue information document does NOT have any information about the opening times of the venue. Queries about opening hours are thus a crossover topic and will be handled in the opening hours document.
ALL QUERIES THAT MENTION ANY PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE SHOULD INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT. EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in json format.
Ensure you follow the following json schema no matter the document or query you are working with:
EXAMPLE JSON OUTPUT:
{{
"reasoning": "This is where you explain your reasoning for the decision you made.",
"decision": "Will be either "include" or "exclude"."
}}
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I leave my drink here and pick it up on my next visit?
### TASK ###
You are responsible for making a decision on whether the venue information document is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
### CROSSOVER TOPICS THAT ARE NOT IN THE VENUE INFORMATION DOCUMENT ###
ALL QUERIES HANDLED BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE VENUE INFORMATION DOCUMENT FROM THE CONTEXT.
If these arise note that the menu doc would NOT be needed as the answer will lie elsewhere, outside of your scope;
RESERVATIONS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
Information on the reservation policies of the venue, this includes;
- Walk in customers seating policy.
- Minimum spends for reserved areas.
- Time limits on reservations.
- Cancellation policys (regarding late arrivals or no shows).
- How groups and large booking are handled.
Other detailed information includes;
- Detailed information on the seating layouts and descriptive information about the different parts of the venue which can be used to compare against the customers requested group size.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
UPCOMING EVENTS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information on the date, time, whether a ticket is needed, and a brief description of the event. Also rules and policies surrounding the specific events.
Any Information asking about upcoming events planned by the business should be referred onto the upcoming events document and thus exclude the venue information document.
MENU DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Pricing ,Ingredients and descriptions of all menu items.(It goes without saying availibility of menu items is not in the venue information document).
- This covers all food, drink and shisha related queries.
- Delivery availability of products, including services like Uber Eats or Foodpanda.
- Takeway of menu items policy.
- Customization of menu items.
- Special offers or happy hours.
- Last orders time for all menu items.
OPENING HOURS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- The 7 day regular working schedule of the venue. Is covered in the opening hours document.
- Last orders time and subsequent closing time for the kitchen, bar etc. Are covered in the opening hours document. Not the venue information document.
Any query that is answered by the opening hours document should not include the venue information document as it would be irrelevant context.
ALL OF THE QUERIES WHICH ARE DIRECTLY ANSWERABLE BY THE CORSSOVER TOPICS SHOULD NOT INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT.
### GUIDELINES ###
If a query asks about a "dining hall", a "theatre" or "bar" or anything that relates to a physical space. We will need the venue information to check if the venue has that space or not. We are not just including conntext to directly answer the querybut also to fact-check if the assumptions made in the query were correct.
Furthermore if the query mentions restrooms, or other facilities that are part of the physical space, the venue informationdocument should be included in the context regardless of the crux of the query.
EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY, IF IT MENTIONS A PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE, THE VENUE INFORMATION DOCUMENT SHOULD BE INCLUDED IN THE CONTEXT.
If a customer mentions wanting to do some form of activity at the venue, like reading a book, studying, working, or having a meeting. The venue information document should be included in the context. As the next node will need to know if the venue has the space to accomodate the customer's request but more importantly it give context on the interior style and ambiance and whether said activity is suitiable.
For example if a customer asks whether its possible to book a private event, the venue information is needed to provide a full a comprehensive answer. As if included, the next node will now be able to provide information on the venues spaces, ammenities and other parts of the physical space that would make it suitiable or not for a private event or custom booking.
The worst case scenario is a customer arrives for a booking but the venue cannot accomodate them due to a policy or physical constraint that was not considered in the response.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking if they can leave their drink and pick it up on their next visit. First, I need to check if this falls under the venue information document. The document covers policies on storing unfinished alcohol. The query is about leaving a drink, which directly relates to that policy.
Also, the guidelines mention that any mention of physical spaces or facilities (like the bar where drinks are served) means the venue document should be included. Even though the main question is about policy, the drink is part of the venue's physical space. So including it ensures the next node can confirm if that's allowed based on their storage policies. There's no overlap with other documents like reservations or menu here. So decision is include.
</think>
{
"reasoning": "The query asks about leaving a drink at the venue and retrieving it later, which directly relates to the venue's policy on storing unfinished alcohol. The venue information document explicitly includes 'Rules around storing unfinished alcohol for later consumption' as part of its contents. Additionally, the query implicitly involves the physical space (e.g., the bar or dining area where the drink is stored), which aligns with the guideline that mentions in physical spaces or facilities require inclusion of the venue information document. There is no indication that this query pertains to crossover topics like reservations, events, menu items, or opening hours.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the venue information document in the prompt is relevant for answering the user query. Ensure you take proper care and consideration to ensure you do not make the wrong decision.
To ensure you are able to make the correct decision, here is a breakdown of what is covered in the venue information document:
VENUE INFORMATION DOCUMENT CONTENTS:
- An abstract/blurb describing the venue.
- Information on location and accessability.
- Information on parking at the venue.
- Interior design and ambiance.
- The seating layout and capacity of the venue.
- The facilities and ammenities available at the venue(eg. wifi, ventillation system, sound system, projectors, restrooms facilites).
- All Information that is related to the physial space wil be in this document - this includes the dining area, bar, theatre, restrooms etc.
- Contact information for additional more complex queries.
- Service charges & all other additional charges.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Dress code.
- Minimum age restrictions.
- Minimum spend policy.
- Rules around patrons using their own decorations on reserved areas.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query is in one of the listed crossover topics, you exclude the document. The reasoning will be explained in the prompt.
The food and drink policy within the venue information document ONLY COVERS the rules and policies around bring in outside food and drinks. And storing unfinished alcohol. All food and drink policy outside of this can be considered crossover topics and will be handled in the menu document.
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude.
The venue information document does NOT have any information about the opening times of the venue. Queries about opening hours are thus a crossover topic and will be handled in the opening hours document.
ALL QUERIES THAT MENTION ANY PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE SHOULD INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT. EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in json format.
Ensure you follow the following json schema no matter the document or query you are working with:
EXAMPLE JSON OUTPUT:
{{
"reasoning": "This is where you explain your reasoning for the decision you made.",
"decision": "Will be either "include" or "exclude"."
}}
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Would it be possible to store my drink for when I return?
### TASK ###
You are responsible for making a decision on whether the venue information document is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
### CROSSOVER TOPICS THAT ARE NOT IN THE VENUE INFORMATION DOCUMENT ###
ALL QUERIES HANDLED BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE VENUE INFORMATION DOCUMENT FROM THE CONTEXT.
If these arise note that the menu doc would NOT be needed as the answer will lie elsewhere, outside of your scope;
RESERVATIONS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
Information on the reservation policies of the venue, this includes;
- Walk in customers seating policy.
- Minimum spends for reserved areas.
- Time limits on reservations.
- Cancellation policys (regarding late arrivals or no shows).
- How groups and large booking are handled.
Other detailed information includes;
- Detailed information on the seating layouts and descriptive information about the different parts of the venue which can be used to compare against the customers requested group size.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
UPCOMING EVENTS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information on the date, time, whether a ticket is needed, and a brief description of the event. Also rules and policies surrounding the specific events.
Any Information asking about upcoming events planned by the business should be referred onto the upcoming events document and thus exclude the venue information document.
MENU DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- Pricing ,Ingredients and descriptions of all menu items.(It goes without saying availibility of menu items is not in the venue information document).
- This covers all food, drink and shisha related queries.
- Delivery availability of products, including services like Uber Eats or Foodpanda.
- Takeway of menu items policy.
- Customization of menu items.
- Special offers or happy hours.
- Last orders time for all menu items.
OPENING HOURS DOCUMENT CONTENTS(ALL OF THIS IS NOT IN THE VENUE INFORMATION DOCUMENT):
- The 7 day regular working schedule of the venue. Is covered in the opening hours document.
- Last orders time and subsequent closing time for the kitchen, bar etc. Are covered in the opening hours document. Not the venue information document.
Any query that is answered by the opening hours document should not include the venue information document as it would be irrelevant context.
ALL OF THE QUERIES WHICH ARE DIRECTLY ANSWERABLE BY THE CORSSOVER TOPICS SHOULD NOT INCLUDE THE VENUE INFORMATION DOCUMENT IN THE CONTEXT.
### GUIDELINES ###
If a query asks about a "dining hall", a "theatre" or "bar" or anything that relates to a physical space. We will need the venue information to check if the venue has that space or not. We are not just including conntext to directly answer the querybut also to fact-check if the assumptions made in the query were correct.
Furthermore if the query mentions restrooms, or other facilities that are part of the physical space, the venue informationdocument should be included in the context regardless of the crux of the query.
EVEN IF THE QUERY IS ABOUT SOMETHING ELSE ENTIRELY, IF IT MENTIONS A PHYSICAL SPACE OR FACILITY THAT IS PART OF THE VENUE, THE VENUE INFORMATION DOCUMENT SHOULD BE INCLUDED IN THE CONTEXT.
If a customer mentions wanting to do some form of activity at the venue, like reading a book, studying, working, or having a meeting. The venue information document should be included in the context. As the next node will need to know if the venue has the space to accomodate the customer's request but more importantly it give context on the interior style and ambiance and whether said activity is suitiable.
For example if a customer asks whether its possible to book a private event, the venue information is needed to provide a full a comprehensive answer. As if included, the next node will now be able to provide information on the venues spaces, ammenities and other parts of the physical space that would make it suitiable or not for a private event or custom booking.
The worst case scenario is a customer arrives for a booking but the venue cannot accomodate them due to a policy or physical constraint that was not considered in the response.
<｜Assistant｜>
<think>
Okay, let me tackle this query. The user is asking if they can store their drink for when they return.
First, I need to check the venue information document's contents. The document includes policies on storing unfinished alcohol. The query is specifically about storing a drink, which falls under the venue's policy on this matter.
Looking at the crossover topics, the menu document handles food and drink offerings, but this isn't about the drink itself—it's about the policy. Since the venue information covers storage policies, it's relevant here. Also, the guidelines mention including the document if the query relates to physical facilities or policies mentioned in the venue info.
No mention of other documents like reservations or opening hours here. The decision should be to include the venue information document because the answer is directly within its policies.
</think>
{
"reasoning": "The query asks about storing a drink for later return, which directly relates to the venue's policy on storing unfinished alcohol. This policy is explicitly covered in the venue information document under the 'Rules on storing unfinished alcohol for later consumption' section. Since the query aligns with documented policies within the venue information, and no crossover topics (e.g., menu items, reservations, events, or opening hours) are involved, the venue information document is necessary to provide an accurate answer.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
End of preview. Expand
in Data Studio
README.md exists but content is empty.
- Downloads last month
- 2