Split (1)

train · 1.32k rows

text stringlengths 6.46k 10.9k
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming sporting events or game screenings. The query falls under the 'upcoming events' category, which is explicitly covered by the Upcoming Events Document. According to the guidelines, any query about events should be directed to that document, leading to an exclusion of the Venue Information Document. However, the guidelines also emphasize including the Venue Information Document when physical spaces or facilities are mentioned, even if the core query is about events. Since the user is asking about events, the primary focus is on the Upcoming Events Document. However, the Venue Information Document contains details about the venue's facilities, which might influence the suitability of hosting such events. Therefore, while the core answer comes from the Upcoming Events Document, the Venue Information Document is still relevant to confirm if the venue can accommodate the events. Thus, the decision is to include the Venue Information Document. </think> { "reasoning": "The query asks about upcoming sporting events or game screenings, which are covered by the Upcoming Events Document. However, the Venue Information Document is required to verify if the venue's facilities (e.g., seating capacity, projectors, sound system) are suitable for hosting such events. Including this document ensures the response considers both event availability and venue capacity.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The query asks about hosting big sporting events or game screenings. This relates to the venue's facilities and capacity. The venue information document includes details on seating layout, capacity, and amenities like projectors, which are essential for hosting such events. Even though upcoming events are handled by another document, the venue's physical space and facilities are crucial for determining suitability. The guidelines emphasize including the venue document when physical space is mentioned, as it provides context for accommodating the event. Therefore, the decision is to include the venue information document. </think> { "reasoning": "The query asks about hosting sporting events or game screenings, which requires checking the venue's facilities and capacity. The venue information document includes details on seating layout, capacity, and amenities like projectors, which are necessary to assess suitability. While upcoming events are covered in another document, the physical space and facilities are critical for answering this query. The guidelines mandate inclusion when physical space or facilities are mentioned, ensuring the next node can verify compatibility.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is asking about events for sports games or screenings. The venue information document doesn't cover upcoming events, which are handled by the upcoming events document. However, the guidelines state that any mention of activities requiring space or facilities necessitates including the venue document. Since the query involves events, the venue document is needed to confirm if the venue has suitable spaces for these activities, such as screens or seating. Even though the events themselves are in the upcoming events document, the venue's facilities are crucial for a comprehensive response. Therefore, the venue document should be included. </think> { "reasoning": "The query asks about events for sports games or screenings. While event details are in the upcoming events document, the venue document is needed to confirm if the venue has suitable spaces like screens, seating, or facilities. The guidelines mandate including the venue document when activities require space or facilities, ensuring the response considers physical constraints and amenities.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The query asks about hosting large-scale sporting events or game screenings. The venue information document is relevant here because it contains details about the venue's facilities, seating capacity, and amenities, which are crucial for determining if the venue can accommodate such events. Even though the upcoming events document handles specific event details, the venue's physical space and infrastructure are essential for answering the query. The guidelines emphasize including the venue document when physical spaces or facilities are mentioned, which applies here. Therefore, the decision is to include the venue information document. </think> { "reasoning": "The query asks about hosting large-scale sporting events or game screenings, which relates to the venue's physical space and facilities. The venue information document contains details about seating capacity, facilities, and amenities, which are necessary to assess whether the venue can accommodate such events. While the upcoming events document covers event specifics, the venue document is required to confirm the physical suitability of the space.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming sporting events or game screenings. The query primarily relates to events, which fall under the upcoming events document. However, the guidelines specify that if the query mentions a physical space or facility, the venue information document should be included. While the main answer comes from the upcoming events document, the venue information is necessary to confirm if the venue has suitable spaces for such events. Additionally, the guidelines emphasize including venue information when activities like screenings are mentioned, even if the primary source is another document. Therefore, the venue information is relevant to provide context on the physical space and facilities, ensuring the response is comprehensive and accurate. </think> { "reasoning": "The query about upcoming sporting events or game screenings primarily relates to the upcoming events document. However, the venue information document is required to verify if the venue has the necessary facilities (e.g., seating, projectors, sound systems) to host such events. This ensures the response accounts for the venue's capabilities, aligning with guidelines that mandate inclusion when physical spaces or facilities are referenced, even if the core answer lies elsewhere.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is asking about events involving major sports games or screenings. The venue information document includes details about facilities and amenities, which are necessary to determine if the venue can host such events. Even though the query is about events, the presence of specific physical spaces (e.g., a screen, seating capacity) is crucial. The guidelines state that any mention of facilities or physical spaces requires including the venue document. Therefore, despite the crossover with the upcoming events document, the venue document is needed to verify the venue's capacity and facilities for hosting events. </think> { "reasoning": "The query asks about events involving sports games or screenings, which requires checking the venue's facilities and amenities. The venue information document includes details about the venue's physical spaces, seating capacity, and facilities like screens or projectors, which are necessary to determine if the venue can host such events. While the events themselves are covered in the upcoming events document, the venue document is essential to confirm the physical space and facilities that support these activities.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about the agenda for big sporting events or game screenings. The query focuses on events, which are typically covered in the upcoming events document. However, the guidelines state that if a query mentions a physical space or facility, the venue information document should be included. The mention of 'sporting events' and 'game screenings' implies that the venue's facilities, such as seating capacity, sound systems, or projectors, might be relevant. Therefore, even though the core answer is in the upcoming events document, the venue information is needed to confirm the suitability of the venue's physical space for such events. Thus, the decision is to include the venue information document. </think> { "reasoning": "The query about big sporting events or game screenings relates to the venue's facilities and physical space. The venue information document contains details about seating capacity, sound systems, and projectors, which are critical for determining the suitability of the venue for such events. Even though the core answer lies in the upcoming events document, the venue information is necessary to confirm the venue's physical capabilities and ensure the response is accurate.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about major sports events or game screenings in the coming weeks. The query falls under the upcoming events document, which handles event details. However, the guidelines specify that if a query mentions a physical space or facility, the venue information document must be included. Although the query does not explicitly mention a physical space, the act of hosting an event in the venue's facilities (like a theater or bar) requires checking the venue's amenities and capacity. Therefore, the venue information document is relevant to confirm if the venue can accommodate such events. </think> { "reasoning": "The query about sports events or game screenings involves checking the venue's facilities and capacity. The venue information document is needed to confirm if the venue has suitable spaces (e.g., a theater or bar) and facilities (e.g., projectors, sound systems) to host such events. This aligns with the guideline that mentions of physical spaces require the venue document for context.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about sporting events or game screenings the venue plans to host. The query is about upcoming events, which falls under the Upcoming Events Document. However, the guidelines state that if the query mentions a physical space or facility, the Venue Information Document should be included. The venue information contains details about facilities like projectors, seating capacity, and ambiance, which are necessary to determine if the venue can accommodate such events. Therefore, even though the query is about events, the Venue Information Document is relevant to ensure the venue can host the event. </think> { "reasoning": "The query asks about sporting events or game screenings, which are covered in the Upcoming Events Document. However, the Venue Information Document is required to verify if the venue has the necessary facilities (e.g., projectors, seating capacity, ambiance) to host such events. This ensures the response accounts for the venue's capabilities and avoids assumptions.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about big game screenings or sporting events at the venue. The query primarily relates to upcoming events, which are covered in the upcoming events document. However, the mention of a physical space (e.g., a screening room) requires checking the venue information document to confirm its availability and suitability. Even though the event details are in another document, the venue information is necessary to ensure the space exists and can accommodate such events. Therefore, including the venue information document is essential for a comprehensive response. </think> { "reasoning": "The query asks about big game screenings or sporting events, which are covered in the upcoming events document. However, the mention of a physical space (e.g., a screening room) necessitates including the venue information document to verify its existence and suitability. This ensures the response accounts for both event availability and venue capacity, aligning with the guideline to include the venue document when physical spaces or facilities are mentioned.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is asking about sports game screenings or major events. The query involves potential events, which falls under the Upcoming Events Document. However, the guidelines specify that any mention of activities requiring physical space or facilities necessitates including the Venue Information Document. Since the query relates to events, the Venue Information Document is relevant to confirm if the venue has suitable spaces, amenities, and policies for such events. Therefore, even though the events are covered in another document, the Venue Information Document is necessary to ensure the venue can accommodate these activities. </think> { "reasoning": "The query about sports game screenings or major events requires checking the venue's facilities and policies. The Venue Information Document includes details on physical spaces, amenities, and policies, which are necessary to confirm suitability for such events. While event details are in the Upcoming Events Document, the Venue Information Document is required to validate the venue's capacity and facilities for hosting these activities.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is asking about upcoming sporting events or game screenings. The venue information document doesn't cover events, which are handled by the upcoming events document. However, the guidelines state that any mention of activities requiring the venue's facilities necessitates including the venue information. Since events like screenings would require specific facilities (e.g., screens, seating), the venue document is needed to confirm availability and suitability. Therefore, the decision is to include the venue information to check if the venue can accommodate such events. </think> { "reasoning": "The query about upcoming sporting events or game screenings relates to the venue's facilities and capacity. The venue information document contains details on facilities like screens, seating, and ambiance, which are crucial for determining if the venue can host such events. Even though the answer might come from the upcoming events document, the venue information is necessary to validate the venue's ability to accommodate these activities, aligning with the guideline that queries mentioning activities requiring facilities necessitate inclusion of the venue information document.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming events for game screenings or sports games. This directly relates to the Upcoming Events Document, which covers special events. The query does not mention a physical space, but the venue information is still relevant because it provides details about the venue's facilities, which are necessary to determine if the venue can accommodate such events. The guidelines state that even if the query is about events, the venue document should be included if it relates to physical space or facilities. Therefore, despite the crossover with the Upcoming Events Document, the venue information is needed to confirm the venue's capacity and amenities for hosting these events. </think> { "reasoning": "The query asks about upcoming events for game screenings or sports games, which falls under the Upcoming Events Document. However, the venue information document is required to confirm whether the venue has the necessary facilities (e.g., seating, projectors, sound systems) to host such events. The guidelines mandate including the venue document when physical spaces or facilities are mentioned, even if the core query is about events.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about big sporting events or game screenings planned for the month. The query relates to upcoming events, which fall under the Upcoming Events Document. However, the guidelines specify that even if the query is about events, the Venue Information Document should be included if a physical space or facility is mentioned. The query does not explicitly mention a physical space, but the Venue Information Document contains details about the venue's facilities, which might be relevant for hosting events. Therefore, including the Venue Information Document ensures that the next node can confirm if the venue has the necessary facilities to host such events, even if the core answer is in the Upcoming Events Document. </think> { "reasoning": "The query asks about planned sporting events or game screenings, which are covered by the Upcoming Events Document. However, the guidelines mandate including the Venue Information Document if any physical space or facility is mentioned, even indirectly. While the query does not explicitly mention a physical space, the Venue Information Document contains details about the venue's facilities, which are crucial for determining if the venue can accommodate such events. This ensures the response accounts for the venue's capabilities, aligning with the guideline to include the document for activity-related queries.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about major sporting events or game screenings in the near future. The query primarily relates to upcoming events, which are covered by the upcoming events document. However, the guidelines specify that if a query involves checking the venue's physical space or facilities, the venue information document should be included. In this case, the user's question implies an interest in using the venue's facilities for events, which necessitates including the venue information document to verify the availability of suitable spaces and amenities. This ensures the response accounts for the venue's capacity, layout, and facilities, even though the core answer about events lies in the upcoming events document. </think> { "reasoning": "The query asks about upcoming sporting events or game screenings, which falls under the upcoming events document. However, the mention of 'screenings' implies the need to check if the venue has suitable facilities (e.g., seating, projectors) for such activities. The venue information document is necessary to confirm the venue's capacity, layout, and amenities, ensuring the response accurately reflects the venue's capabilities for hosting events.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user asks about upcoming plans for showing big sporting events or game screenings. The query falls under the 'upcoming events' category, which is handled by the Upcoming Events Document. However, the guidelines specify that if the query mentions a physical space or facility, the Venue Information Document should be included. The Venue Information Document contains details about the venue's facilities, such as seating capacity and amenities, which are necessary to determine if the venue can accommodate such events. Additionally, the guidelines state that even if the main answer is in another document, the Venue Information Document should be included if physical spaces or facilities are referenced. Therefore, the decision is to include the Venue Information Document to ensure the venue's suitability for hosting the events is considered. </think> { "reasoning": "The query asks about upcoming sporting events or game screenings, which are covered in the Upcoming Events Document. However, the Venue Information Document is required to verify if the venue's facilities (e.g., seating capacity, sound systems, projectors) can accommodate these events. This ensures the venue's suitability for hosting such activities is factored into the response.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming sports game screenings or events. This query falls under the 'Upcoming Events Document' as it relates to events hosted by the venue. The guidelines specify that queries about events should be directed to the upcoming events document, which is a crossover topic. However, the venue information document is required to confirm if the venue has suitable facilities for such events. The guidelines emphasize including the venue document when physical spaces or facilities are mentioned, even if the query is about events. Since the user is asking about events, the venue document is necessary to verify if the venue can accommodate these activities. Therefore, the decision is to include the venue information document to ensure the response is accurate and considers the venue's capabilities. </think> { "reasoning": "The query asks about upcoming sports game screenings or events, which are covered by the upcoming events document. However, the venue information document is required to confirm if the venue has suitable facilities for such activities. Guidelines specify that even if the query is about events, the venue document must be included to verify physical space and amenities. This ensures the response is accurate and considers the venue's capabilities.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user asks about upcoming screenings or sporting events. The venue information document doesn't cover events, which are handled by the upcoming events document. However, the guidelines state that any mention of a physical space or facility requires including the venue document. The query doesn't explicitly mention a physical space, but the venue's facilities (like screens, seating, or sound systems) might be necessary to assess suitability for events. Since the venue document includes details about facilities, it should be included to provide context on whether the venue can host such events. Additionally, the guidelines emphasize including the venue document when activities like screenings are mentioned, as it relates to the venue's capabilities. Therefore, even though the query is about events, the venue information is needed to ensure the venue's infrastructure supports the events. </think> { "reasoning": "The query asks about upcoming screenings or sporting events, which are covered by the upcoming events document. However, the guidelines specify that any mention of physical spaces or facilities (e.g., screens, seating, sound systems) requires including the venue information document. This ensures the next node can verify if the venue's facilities are suitable for hosting such events, even if the core answer lies elsewhere. The venue document provides context on the venue's infrastructure, which is crucial for answering the query accurately.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming plans for big game screenings or sports events. This directly relates to the venue's events, which are covered in the upcoming events document. However, the venue information document is needed to confirm if the venue can accommodate such events, considering factors like seating capacity, facilities, and policies. Even though the query is about events, the venue document is crucial for verifying physical space availability and suitability. Therefore, including the venue document ensures the response is accurate and addresses potential constraints. </think> { "reasoning": "The query asks about upcoming plans for big game screenings or sports events. While the upcoming events document covers event details, the venue information document is necessary to confirm if the venue's physical space and facilities can accommodate these events. This ensures the response accounts for policies, seating capacity, and other constraints related to the venue's physical infrastructure.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about major sports events or game screenings happening at the venue soon. This query primarily relates to upcoming events, which are covered by the Upcoming Events Document. However, the guidelines specify that if the query mentions a physical space or facility, the Venue Information Document should be included. Since the question involves checking if the venue has suitable facilities for such events, the Venue Information Document is necessary to verify the presence of appropriate spaces like a screen or seating area. Therefore, even though the core answer lies in the Upcoming Events Document, the Venue Information Document is required to confirm the venue's capabilities. </think> { "reasoning": "The query asks about major sports events or game screenings, which are covered in the Upcoming Events Document. However, the mention of 'screenings' implies the need to check if the venue has suitable facilities like a screen or seating area. The Venue Information Document contains details about facilities and amenities, which are necessary to confirm the venue's ability to host such events. Therefore, the Venue Information Document should be included to ensure accurate and comprehensive response.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about special plans for game screenings or sporting events this month. The query relates to events, which are covered in the upcoming events document. However, the guidelines state that even if the crux of the query is about events, mentioning a physical space or facility requires including the venue information. Since the question involves hosting an event, the venue's facilities and capacity are crucial for determining suitability. Therefore, the venue information document should be included to assess the venue's ability to accommodate such events, even though the core answer is in the upcoming events document. </think> { "reasoning": "The query asks about special plans for game screenings or sporting events, which are covered in the upcoming events document. However, the venue information document is necessary to assess the venue's facilities and capacity for hosting such events. The guidelines specify that queries involving activities like hosting events require the venue information to ensure the physical space is suitable. Thus, the venue document should be included to provide context on facilities and ambiance.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about events involving large sporting events or game screenings. The query relates to events, which are covered in the Upcoming Events Document. However, the guidelines state that if the query mentions a physical space or facility, the Venue Information Document should be included. The user's question is about hosting such events, which implies needing information about the venue's capacity, facilities, and amenities. The Venue Information Document contains details about seating capacity, facilities, and ambiance, which are essential for determining if the venue can host such events. Therefore, even though the event details are in another document, the Venue Information Document is necessary to confirm the venue's suitability for hosting these events. </think> { "reasoning": "The query asks about events involving large sporting events or game screenings. While event details are covered in the Upcoming Events Document, the Venue Information Document is required to confirm the venue's capacity, facilities, and ambiance for hosting such events. This ensures the next node can verify if the physical space and amenities are suitable for the requested activities.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is asking about upcoming sporting events or game screenings at the venue. The query relates to events, which falls under the upcoming events document. However, the guidelines state that if the query mentions a physical space or facility, the venue information document should be included. Since the user is inquiring about events, the venue information is necessary to confirm if the venue has suitable spaces like a bar or theatre. Additionally, the guidelines emphasize including venue information to ensure the next node can address both the event details and the physical space requirements. Therefore, the decision is to include the venue information document. </think> { "reasoning": "The query asks about upcoming sporting events or game screenings, which are covered in the upcoming events document. However, the guidelines specify that if the query mentions a physical space or facility, the venue information document must be included. This ensures the next node can verify if the venue has suitable spaces (e.g., a bar or theatre) for such events, aligning with the requirement to include the venue document for activity-related queries.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about major sports screenings or game events in the near future. This query relates to events, which falls under the upcoming events document. However, the guidelines state that if the query involves activities or events, the venue information document should be included to check for suitable spaces. The venue document provides details on facilities like seating capacity and ambiance, which are relevant for hosting such events. Therefore, including the venue information document ensures that the next node can verify if the venue has the necessary amenities to accommodate these events. </think> { "reasoning": "The query about major sports screenings or game events relates to upcoming events, which are covered in the upcoming events document. However, the venue information document is needed to confirm if the venue's physical spaces (e.g., seating capacity, facilities) are suitable for hosting such events. This aligns with the guideline that queries involving activities or events require the venue document to assess suitability.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> Okay, let's break this down. The user is asking if there are any big events planned for game screenings or sports. First, I need to check which document handles this query. The upcoming events document covers special events, weekly/monthly events, and their details like dates, times, tickets, etc. Since the question is about planned events, the answer would be in the upcoming events document, not the venue information. But wait, the guidelines say that if a query mentions a physical space or facility, the venue document should be included. Even if the main answer is elsewhere, mentioning an event might relate to the venue's facilities. For example, a game screening might require a specific area with screens, seating, or amenities. The venue document includes info on facilities like projectors, sound systems, or seating capacity. Without checking the venue info, we can't confirm if the venue has the necessary setup for such an event. Also, the guidelines emphasize including venue info when activities like screenings or sports require checking the physical space. Even though the main answer is in another document, the venue info is needed to ensure the space can accommodate the event. So including it helps the next node provide a comprehensive response, confirming both the existence of the event and the venue's suitability. </think> { "reasoning": "The query asks about planned events (game screenings or sports), which are covered in the upcoming events document. However, the venue information document is required to confirm whether the venue has the necessary facilities (e.g., screens, seating, sound systems) to accommodate such events. The guidelines explicitly state that queries mentioning activities requiring physical space or facility details should include the venue information document to ensure context for suitability and feasibility.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about major sports events or game screenings scheduled for this month. This falls under the upcoming events document, which handles all event-related queries. However, the guidelines specify that if the query mentions a physical space or facility, the venue information document must be included. Although the query does not explicitly mention a physical space, the mention of "scheduling" suggests the need to verify if the venue has the necessary facilities to host such events. The venue information document contains details about facilities like seating, capacity, and amenities, which are crucial for determining if the venue can accommodate these events. Therefore, including the venue information document is necessary to ensure the response considers the venue's capabilities. </think> { "reasoning": "The query about scheduled sports events or game screenings requires checking the venue's facilities and capacity to ensure they can accommodate such activities. The venue information document contains details about seating layout, capacity, and amenities like projectors and sound systems, which are essential for confirming suitability. Even though the query relates to events, the venue document is needed to validate physical space and facilities for hosting the events.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about big sporting events or game screenings. The venue information document does not cover events, which are handled by the upcoming events document. However, the guidelines state that if the query mentions a physical space or facility, the venue document should be included. Since the user is asking about events, the venue document is still relevant for checking if the venue has the necessary facilities like screens, seating, or amenities to host such events. This ensures that the response accounts for the venue's capacity and infrastructure, even though the event details are in the upcoming events document. </think> { "reasoning": "The query asks about big sporting events or game screenings, which are covered in the upcoming events document. However, the venue information document is needed to confirm if the venue has the physical space, facilities, and amenities (e.g., screens, seating capacity) suitable for hosting such events. This ensures the response considers the venue's capabilities, even though the event details are elsewhere.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about big screenings for sporting events or games soon. This relates to upcoming events, which are covered in the Upcoming Events document. However, the query also mentions the need to check if the venue has the necessary facilities for such screenings. The Venue Information document contains details about the venue's facilities, including projectors and seating capacity, which are essential to determine if the venue can accommodate the event. Therefore, including the Venue Information document is necessary to ensure the next node can confirm the venue's suitability for the event. </think> { "reasoning": "The query asks about big screenings for sporting events or games, which falls under the Upcoming Events document. However, the mention of the need to check if the venue can accommodate such screenings necessitates including the Venue Information document. This document contains details about facilities like projectors and seating capacity, which are critical for confirming the venue's suitability for the event. Including it ensures the next node can verify the venue's infrastructure before addressing the event details.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about the schedule for game screenings or sporting events in the upcoming weeks. This query falls under upcoming events, which are covered by the Upcoming Events Document. However, the guidelines specify that if the query mentions a physical space or facility, the Venue Information Document should be included. Since the question is about events hosted in the venue, the Venue Information Document is necessary to confirm the existence of suitable spaces and facilities, even if the event details are in another document. Therefore, including the Venue Information Document is essential to ensure accurate information about the venue's capacity and amenities for hosting such events. </think> { "reasoning": "The query asks about game screenings or sporting events in the upcoming weeks, which relates to events hosted at the venue. The Upcoming Events Document covers event schedules, while the Venue Information Document is needed to confirm the venue's capacity, facilities, and policies for hosting such activities. This ensures the response accounts for the venue's physical space and suitability for events.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about large-scale sports events or game screenings at the venue. The query directly relates to events, which are covered by the upcoming events document. However, the guidelines specify that if a query mentions a physical space or facility, the venue information document should be included. The mention of a "large-scale event" implies the need to check if the venue has suitable facilities, such as a large screen or seating capacity. Therefore, including the venue information document is necessary to confirm if the venue can accommodate such events. </think> { "reasoning": "The query asks about large-scale sports events or game screenings, which are covered by the upcoming events document. However, the mention of 'large-scale' suggests the need to verify the venue's facilities, such as screens or seating capacity, which are part of the venue information document. Including it ensures the next node can confirm suitability and provide accurate context.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is asking about upcoming events involving major sporting events or game screenings. The query falls under the 'upcoming events' category, which is handled by the Upcoming Events Document. However, the guidelines state that if the query mentions a physical space or facility, the Venue Information Document should be included. Although the query doesn't explicitly mention a physical space, the presence of events requires checking the venue's facilities and seating capacity to ensure they can accommodate such activities. Therefore, the Venue Information Document is relevant to provide context on the venue's capabilities for hosting events. </think> { "reasoning": "The query asks about upcoming events involving sporting events or game screenings. While the Upcoming Events Document covers event details, the Venue Information Document is necessary to confirm the venue's facilities (e.g., seating capacity, screen size) and physical space suitability for hosting such events. This ensures the response accounts for the venue's capacity and amenities, aligning with the guideline to include the Venue Information Document when activities require physical space considerations.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about big game screenings or sporting events planned for the weekend. This query primarily relates to events, which are covered by the upcoming events document. However, the guidelines specify that if a query mentions a physical space or facility, the venue information document should be included. Since the venue's facilities (e.g., screen size, seating capacity, sound system) are crucial for hosting such events, the venue document is necessary to confirm if the venue can accommodate these activities. Therefore, despite the crossover with the events document, the mention of facilities necessitates including the venue information. </think> { "reasoning": "The query asks about big game screenings or sporting events, which are typically covered by the upcoming events document. However, the mention of 'screening' and 'sporting events' implies the need to assess the venue's facilities (e.g., screen size, seating capacity, sound system) to determine suitability. The venue information document contains details about the venue's physical spaces and facilities, which are essential for evaluating the feasibility of hosting such events. Therefore, including the venue information document ensures the next node can address the query comprehensively.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming game screenings or sporting events. This relates to events, which are covered in the Upcoming Events Document. However, the query also implicitly involves the venue's facilities and capacity. The Venue Information Document includes details about facilities like sound systems, seating capacity, and ambiance, which are crucial for hosting such events. Additionally, the guidelines state that any mention of activities requiring space or facilities necessitates including the Venue Information Document. Therefore, despite the event details being in the Upcoming Events Document, the Venue Information Document is still relevant to confirm suitability for the event. </think> { "reasoning": "The query about upcoming game screenings or sporting events pertains to events hosted at the venue. While the Upcoming Events Document contains event specifics, the Venue Information Document is necessary to confirm facility suitability, including capacity, ambiance, and facilities like sound systems. The guidelines mandate inclusion when activities require venue infrastructure, ensuring the response accounts for physical space and amenities.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The query asks about major game screenings or sports events on the calendar. The venue information document doesn't cover events, which are handled by the upcoming events document. However, the guidelines state that any mention of activities requiring physical space (like events) necessitates including the venue document to verify if suitable facilities exist. Since the user is inquiring about events, the next node needs to check if the venue has the necessary space and amenities, such as a screen or seating capacity, which are covered in the venue information. Therefore, despite the events being in another document, the venue document is still relevant to confirm the physical capabilities. </think> { "reasoning": "The query about game screenings or sports events requires checking the venue's facilities and capacity, which are detailed in the venue information document. Even though event details are in the upcoming events document, the venue document is necessary to confirm physical suitability for such activities. The guidelines mandate including the venue document for queries involving activities requiring space, ensuring the response accounts for physical constraints.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming sporting events or game screenings. The venue information document does not cover events, which are handled by the upcoming events document. However, the guidelines state that any mention of an activity (like screenings) necessitates including the venue document to assess suitability. Since the user is asking about events, the venue document is still relevant to confirm if the venue has the necessary facilities, such as screens or seating, to host such events. Therefore, the venue information document should be included to provide context on the physical space and facilities required for these screenings. </think> { "reasoning": "The query asks about upcoming sporting events or game screenings. While event details are covered in the upcoming events document, the venue information document is required to confirm if the venue has the necessary facilities (e.g., screens, seating capacity) to host such events. The guidelines mandate inclusion when activities like screenings require physical space verification, ensuring the response accounts for suitability.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The query asks about events for game screenings or sporting events. The venue information document includes details on facilities like sound systems, seating capacity, and amenities, which are essential for hosting such events. The upcoming events document covers event specifics, but the venue document is needed to confirm if the physical space and facilities can accommodate these activities. Since the query involves activities at the venue, the venue document is relevant for assessing suitability. Therefore, including it ensures a comprehensive response. </think> { "reasoning": "The query asks about events for game screenings or sporting events. While the upcoming events document covers event details, the venue information document is essential to verify if the physical space and facilities (e.g., sound system, seating capacity) can accommodate these activities. This ensures the response considers the venue's suitability for the requested events.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming sports events or game screenings. This relates to the upcoming events document, which covers special events. However, the query mentions a potential need to check if the venue can accommodate such activities. The venue information document includes details on facilities, seating capacity, and amenities, which are essential to determine if the venue can host events. Additionally, the guidelines state that any mention of activities requiring physical space necessitates including the venue document. Therefore, even though the query is about events, the venue information is relevant to ensure the venue can host the activities described. </think> { "reasoning": "The query asks about upcoming sports events or game screenings, which are covered in the upcoming events document. However, the mention of hosting activities at the venue requires checking the venue information document to confirm the physical space and facilities can accommodate such events. Guidelines state that any activity-related queries necessitate including the venue document to assess suitability and provide context about the venue's capabilities.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about sporting events or game screenings hosted this month. This falls under the 'upcoming events document' which covers monthly events. However, the guidelines specify that if the query mentions a physical space or facility, the venue information document must be included. While the query doesn't explicitly mention a physical space, the venue's facilities (like seating capacity, projectors, or ambiance) are crucial for hosting such events. The venue information document contains details about the venue's capacity and facilities, which are necessary to determine if the venue can accommodate the event. Therefore, even though the main answer lies in the upcoming events document, the venue information is needed to confirm the venue's suitability for the event. </think> { "reasoning": "The query asks about sporting events or game screenings this month. While the main answer lies in the upcoming events document, the venue information document is required to confirm the venue's facilities (e.g., seating capacity, projectors) and policies (e.g., minimum spend, decoration rules) that are critical for hosting such events. The guidelines mandate inclusion when queries involve physical spaces or facilities, even if the primary answer source is elsewhere.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about big game screenings or sporting events planned for this month. This query directly relates to the venue's upcoming events, which are covered in the Upcoming Events Document. The guidelines state that queries about events should be directed to that document, and the Venue Information Document is excluded. However, the guidelines also emphasize including the Venue Information Document if the query involves checking the venue's physical spaces or facilities. The user's query about events suggests the need to confirm if the venue has suitable spaces for screenings, which is covered in the Venue Information Document. Therefore, despite the event details being in the Upcoming Events Document, the Venue Information Document is still relevant to ensure the venue can accommodate the event. </think> { "reasoning": "The query about big game screenings or sporting events requires confirming if the venue has suitable physical spaces and facilities. The Venue Information Document contains details about the venue's facilities and capacity, which is essential to determine if the venue can host such events. While event specifics are in the Upcoming Events Document, the Venue Information Document is necessary to validate the venue's capability.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about large sporting events or game screenings. This falls under the upcoming events document, which covers planned events. However, the guidelines state that if the query mentions a physical space or facility, the venue information document must be included. Although the query does not explicitly mention a physical space, the venue's facilities, such as seating capacity and available screens, are crucial for determining if such events can be accommodated. Therefore, the venue information document should be included to provide context on the venue's capacity and facilities, ensuring an accurate response about event suitability. </think> { "reasoning": "The query asks about planned events, which is covered by the upcoming events document. However, the venue information document is required to confirm if the venue has the necessary facilities (e.g., screens, seating capacity) to accommodate such events. This ensures the response is accurate and considers the venue's physical capabilities.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is asking about hosting big sporting events or game screenings. The query involves an activity (sporting events) that requires checking the venue's facilities and capacity. The venue information document includes details about facilities like seating, capacity, and amenities, which are crucial for hosting such events. Additionally, the guidelines state that any mention of activities requiring space necessitates including the venue document. Therefore, even though the query is about events, the venue's physical aspects are essential for a comprehensive answer. </think> { "reasoning": "The query about hosting big sporting events or game screenings relates to the venue's physical space, facilities, and capacity. The venue information document contains details about seating layout, capacity, and amenities necessary for such events. Including this document ensures the next node can verify if the venue can accommodate the activity and provide suitable facilities.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming sports events or game screenings. This falls under the 'upcoming events' category, which is handled by a separate document. However, the guidelines state that any mention of activities or events at the venue necessitates including the venue information document. Since the query involves events, the venue's facilities and policies, such as seating capacity and amenities, are crucial for determining if the venue can accommodate such activities. Therefore, the venue information document should be included to provide context about the physical space and facilities needed for the events. </think> { "reasoning": "The query asks about scheduled sports events or game screenings, which are covered in the 'upcoming events' document. However, the venue information document is required to verify if the venue has the necessary facilities (e.g., seating, screen size, amenities) to host these events. This ensures the response accounts for the physical space's suitability, aligning with the guideline to include the venue document when activities or events are mentioned.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user asks about upcoming sports games or screenings at the venue. This relates to events, which are covered in the Upcoming Events Document. However, the query mentions the venue's facilities, which are part of the Venue Information Document. Guidelines state that if a query involves a physical space or facility, the Venue Information Document must be included. The mention of facilities like a screen or seating area is crucial for determining if the venue can host such events. Therefore, even though the core answer is in the Upcoming Events Document, the Venue Information Document is needed to confirm the availability of the necessary facilities. </think> { "reasoning": "The query about upcoming sports games or screenings requires checking the venue's facilities (e.g., screens, seating, amenities). The Venue Information Document is essential to confirm if the venue has suitable spaces and equipment for such events, even though the core answer about events is in the Upcoming Events Document. The guidelines mandate including the Venue Information Document when physical spaces or facilities are mentioned, ensuring the response accounts for the venue's capabilities.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about plans for showing major sporting events or game screenings. The query directly relates to events, which are covered in the Upcoming Events Document. However, the guidelines specify that if a query involves an activity or event that requires checking the venue's facilities, the Venue Information Document should be included. Since the user is asking about event screenings, the Venue Information Document is necessary to confirm if the venue has suitable facilities like screens, seating, or capacity, which are essential for hosting such events. Therefore, despite the primary answer being in the Upcoming Events Document, the Venue Information Document is included to ensure the next node can verify the physical space's suitability. </think> { "reasoning": "The query asks about plans for showing sporting events or game screenings. While the Upcoming Events Document handles event details, the Venue Information Document is required to verify if the venue has the necessary facilities (e.g., screens, seating capacity) to accommodate these screenings. This ensures the response considers both event logistics and venue capabilities.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about game screenings or sporting events happening soon. This query falls under the upcoming events document, which handles special events. However, the guidelines state that if a query mentions a physical space or facility, the venue information document should be included. The mention of an event implies the need to check if the venue has suitable facilities for such activities. The venue document provides details on seating, capacity, and amenities, which are necessary to determine if the venue can accommodate these events. Therefore, including the venue information document is essential to ensure the response accurately reflects the venue's capabilities. </think> { "reasoning": "The query asks about game screenings or sporting events, which are covered in the upcoming events document. However, the mention of 'happening soon' implies a need to verify the venue's facilities (e.g., seating capacity, sound system) to ensure suitability. The venue information document contains critical details about the venue's physical space and amenities, which are essential for evaluating the possibility of hosting such events. Including this document ensures the response accounts for the venue's capabilities.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming sporting events or game screenings at the venue. This query pertains to events, which are covered in the Upcoming Events Document. However, the venue information document is necessary to confirm if the venue has the facilities to host such events, such as seating capacity, sound systems, or projectors. The guidelines state that even if the crux of the query is about events, mentioning facilities requires including the venue document. Therefore, the venue information should be included to ensure the venue's capabilities are considered. </think> { "reasoning": "The query asks about sporting events or game screenings, which are covered by the Upcoming Events Document. However, the venue information document is required to confirm whether the venue has the necessary facilities (e.g., seating capacity, sound systems, projectors) to host such events. The guidelines mandate inclusion when physical space or facilities are mentioned, even if the core query is about events.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user asks about game screenings or sporting events. The venue information document includes details on facilities and amenities, which are crucial for hosting such events. Even though the query is about upcoming events, the venue document is needed to confirm if the venue has suitable spaces and facilities, such as projectors, seating capacity, and sound systems. This ensures the response accounts for the physical aspects required for the events, aligning with the guidelines that require including the venue document when activities like screenings are mentioned. </think> { "reasoning": "The query about game screenings or sporting events requires checking the venue's facilities and amenities, which are covered in the venue information document. This ensures the response accounts for the physical space and equipment needed for such activities, aligning with guidelines that mandate inclusion when activities like screenings are mentioned.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming sporting events or screenings this month. The query falls under the 'Upcoming Events Document' category, which handles event details like dates, times, and descriptions. However, the guidelines specify that if the query mentions a physical space or facility, the venue information document should be included. Since the user is asking about events, the venue document is still necessary to confirm if the venue has the necessary facilities, such as screens or seating capacity, to host such events. Therefore, even though the core answer is in the upcoming events document, the venue information is required to ensure the venue can accommodate the events. </think> { "reasoning": "The query asks about upcoming sporting events or screenings, which are covered in the upcoming events document. However, the venue information document is needed to confirm if the venue has the necessary facilities (e.g., screens, seating capacity) to host these events. Including the venue document ensures the next node can verify compatibility with the venue's physical capabilities.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming big game screenings or sporting events at the venue. The query directly relates to events, which are covered in the upcoming events document. However, the guidelines specify that even if the query is about events, the venue information document should still be included if it involves checking the physical space or facilities. Since the query implies the need for a suitable space (e.g., a screening room), the venue document is necessary to confirm the existence of such a facility and its amenities. Therefore, despite the crossover with the upcoming events document, the venue information is relevant to ensure the venue can accommodate the event. </think> { "reasoning": "The query about upcoming big game screenings or sporting events relates to the venue's facilities and capacity. While event details are in the upcoming events document, the venue information is needed to confirm the venue's physical space and amenities (e.g., projectors, seating capacity) to ensure suitability for hosting such events. This aligns with guidelines requiring inclusion when physical space or facilities are mentioned, even if the core query is about events.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about major sporting events or game screenings scheduled soon. The venue information document does not cover upcoming events, as that is handled by the upcoming events document. However, the guidelines state that any mention of an activity requiring the venue's facilities necessitates including the venue information. Since events like screenings require knowledge of the venue's facilities (e.g., screen size, seating capacity, sound system), the venue document is relevant. The query's core is about events, but the mention of screenings implies a need to confirm the venue's capacity and facilities, which are covered in the venue information. Therefore, including the venue document is necessary to ensure the response accurately reflects the venue's capabilities. </think> { "reasoning": "The query asks about upcoming sporting events or game screenings, which are covered in the upcoming events document. However, the mention of 'screenings' implies the need to confirm the venue's facilities (e.g., screen size, seating capacity, sound system) to ensure suitability for such activities. The venue information document contains details about the physical space and facilities, which are critical for answering the query accurately. Therefore, including the venue information document is necessary to provide context about the venue's capabilities.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming live performances, art exhibitions, or community gatherings. These are events, which are covered in the Upcoming Events Document. The Venue Information Document does not contain event details, but it includes facilities like seating capacity and ambiance. Since the query mentions activities that require space and facilities, the Venue Information Document is necessary to confirm the venue's suitability for these events. Even though the events themselves are in the Upcoming Events Document, the physical space and amenities are part of the Venue Information Document. Therefore, the decision is to include the Venue Information Document to ensure the venue can accommodate the requested activities. </think> { "reasoning": "The query asks about upcoming live performances, art exhibitions, or community gatherings. These are covered in the Upcoming Events Document, but the Venue Information Document is required to verify the venue's facilities and suitability for such activities. The document contains details on seating capacity, ambiance, and physical space, which are crucial for answering the query accurately.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about plans for hosting concerts, theater performances, or art shows. This relates to the venue's capacity, facilities, and policies. The venue information document includes details on seating layout, capacity, and amenities, which are necessary to determine if the venue can accommodate such events. Additionally, the guidelines specify that any mention of hosting activities requires including the venue document to check physical space and policies. Since the query involves hosting events, the venue document is essential to confirm suitability and provide context for the response. </think> { "reasoning": "The query about hosting concerts, theater performances, or art shows directly relates to the venue's capacity, facilities, and policies. The venue information document contains details about seating layout, capacity, and amenities, which are critical for determining suitability. Additionally, guidelines mandate inclusion when queries involve hosting activities, ensuring the response accounts for physical space and policies. This aligns with the need to verify the venue's capabilities to accommodate such events.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about events for live music, theater productions, or corporate conferences. The venue information document contains details on facilities, such as seating capacity, ambiance, and amenities, which are crucial for determining suitability. While the upcoming events document covers specific events, the venue document is needed to confirm if the venue can accommodate these activities. The guidelines state that any mention of activities requiring physical space necessitates including the venue document. Therefore, even though the query is about events, the venue document is necessary to verify the physical capabilities and ambiance for hosting such events. </think> { "reasoning": "The query asks about events for live music, theater productions, or corporate conferences, which relate to the venue's facilities and capacity. The venue information document is necessary to confirm if the venue can accommodate these activities, as it includes details about seating capacity, ambiance, and amenities. While the upcoming events document covers event details, the venue document is required to validate the physical space and suitability for these events.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming large-scale concerts, theater performances, or business events. The venue information document does not cover events, which are handled by the upcoming events document. However, the guidelines state that any mention of activities requiring physical space necessitates including the venue document. Since the query involves potential events, the venue document is needed to confirm if the venue can accommodate such activities, considering facilities like seating, sound systems, and capacity. Thus, including the venue document is essential to provide an accurate response about the venue's suitability for these events. </think> { "reasoning": "The query asks about upcoming large-scale events, which are covered in the upcoming events document. However, the venue information document is required to confirm if the venue's physical space and facilities (e.g., seating capacity, sound system, and amenities) can accommodate these events. This ensures the response accurately reflects the venue's capabilities for hosting such activities.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming performances, live shows, or cultural festivals. The query directly relates to events, which are covered in the Upcoming Events Document. However, the guidelines specify that if the query involves activities requiring physical space, the Venue Information Document should be included. Since the user is asking about performances, the venue's facilities and seating capacity are necessary to determine if they can accommodate such events. The Venue Information Document contains details about the physical space, which is essential for answering the query accurately. </think> { "reasoning": "The query asks about upcoming performances, live shows, or cultural festivals, which fall under the Upcoming Events Document. However, the mention of activities requiring physical space (e.g., stage setup, audience capacity) necessitates including the Venue Information Document. This ensures the next node can verify if the venue has suitable facilities and capacity to host these events, aligning with the guideline that queries about activities necessitate venue information.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> Okay, let's tackle this query. The user is asking about events organized by the venue, specifically mentioning music concerts, art exhibitions, or special workshops. First, I need to check if the venue information document is relevant here. The guidelines say that if the query is about events, the upcoming events document should handle it. But wait, the crossover topics mention that all queries about upcoming events should exclude the venue info. However, the guidelines also state that even if the query is about events, if it mentions a physical space or facility, the venue document should be included. The query here is about events, but the user might be planning to use the venue's facilities for these events. For example, if a workshop is happening, the venue might need to know if there's a suitable space, like a theatre or a specific area. The venue document includes details on facilities like seating, capacity, and amenities, which are crucial for determining if the venue can host such events. Additionally, the guidelines emphasize including the venue document when activities like workshops or exhibitions are mentioned, as it helps assess the suitability of the physical space. Even though the events themselves are covered in the upcoming events document, the venue info is needed to confirm the venue's capacity and facilities. So, even though the main answer about events would come from the upcoming events doc, the venue info is necessary to provide context on the physical space and facilities. Therefore, the decision is to include the venue information document. </think> { "reasoning": "The query asks about events involving music concerts, art exhibitions, or workshops, which are classified as 'upcoming events' handled by the upcoming events document. However, the guidelines specify that even if the crux of the query is about events, mentioning activities requiring physical space or facility use necessitates including the venue information document. The venue document contains details about seating capacity, facilities, and amenities (e.g., sound systems, projectors), which are critical to determine if the venue can accommodate these activities. While the event details are in the upcoming events document, the venue document is required to verify physical space suitability and facilities.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about the agenda for live performances, art installations, or creative workshops. The venue information document contains details about facilities and amenities, which are crucial for determining if the venue can host such events. While the upcoming events document handles specific event details, the venue document is needed to confirm the physical space and facilities for these activities. The guidelines emphasize including the venue document when activities like workshops or performances are mentioned, as it provides context on the venue's capabilities. Therefore, the decision is to include the venue information document. </think> { "reasoning": "The query asks about live performances, art installations, or creative workshops, which relate to the venue's physical space and facilities. The venue information document contains details about seating capacity, facilities, and ambiance, which are necessary to confirm if the venue can accommodate these activities. While the upcoming events document covers specific event details, the venue document is essential to validate the physical suitability and support for these activities.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about theater performances, corporate seminars, or live concerts in the coming weeks. These events are typically covered in the upcoming events document, which is a crossover topic. However, the venue information document is necessary to confirm the availability of suitable spaces like theaters or performance areas. The guidelines state that any mention of physical spaces or facilities requires inclusion of the venue document. Even though the query is about events, the venue's facilities are crucial to ensure the venue can accommodate these activities. Therefore, including the venue document is essential to validate the physical space and related policies. </think> { "reasoning": "The query asks about theater performances, corporate seminars, or live concerts, which are events. While these are covered in the upcoming events document, the venue information document is necessary to confirm the venue's facilities and physical spaces like theaters or performance areas. This ensures the venue can accommodate such activities, aligning with the guideline that any mention of physical spaces requires inclusion of the venue document.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about events like live music, art shows, or workshops. The query does not explicitly mention a physical space, but the guidelines state that if the activity requires the venue's facilities, the venue document should be included. Since events like live music or workshops may require specific spaces or amenities, the venue document is necessary to confirm availability and suitability. Additionally, the upcoming events document covers details about specific events, but the venue document is essential for context on the physical space and facilities. Therefore, including the venue document is crucial to provide a comprehensive response. </think> { "reasoning": "The query asks about events like live music, art shows, or workshops, which may require the venue's physical spaces and facilities. The venue document contains information on seating capacity, ambiance, and amenities, which are critical for determining suitability. While the upcoming events document covers event details, the venue document is necessary to confirm availability and facility details. The guidelines mandate inclusion when activities depend on physical space or facilities.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming performances, comedy shows, or corporate events at the venue. The query is about events, which falls under the Upcoming Events Document. However, the guidelines state that if the query mentions a physical space or facility, the Venue Information Document should be included. Since the user is asking about events, the Venue Information Document is necessary to confirm if the venue has suitable spaces for these activities. Even though the main answer comes from the Upcoming Events Document, the Venue Information Document is required to ensure the venue's physical capabilities are considered. Therefore, the decision is to include the Venue Information Document. </think> { "reasoning": "The query asks about upcoming performances, comedy shows, or corporate events, which are covered by the Upcoming Events Document. However, the guidelines specify that if the query mentions a physical space or facility, the Venue Information Document must be included. This ensures the next node can verify if the venue's spaces (e.g., theatre, bar, or private areas) are suitable for these events. While the core answer comes from the Upcoming Events Document, the Venue Information Document is necessary to confirm the venue's physical capabilities, aligning with the guidelines.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about live theater, musical performances, or local art exhibitions. The venue information document is crucial here because it details the facilities and amenities that would support such events. Even though upcoming events are handled by a different document, the venue information is needed to confirm the physical space and facilities, which are essential for hosting these activities. The guidelines emphasize including the venue document when activities require space or facilities, ensuring the next node can accurately assess suitability. </think> { "reasoning": "The query asks about planned events like live theater, musical performances, or art exhibitions. While upcoming events are covered in the Upcoming Events Document, the venue information document is necessary to confirm the physical space and facilities that can accommodate such activities. The guidelines specify that queries involving activities requiring space or facilities necessitate including the venue document to ensure accurate context for the next node's response.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming art exhibitions, music concerts, or cultural performances. These events fall under the 'upcoming events' category, which is covered by a separate document. However, the guidelines specify that if a query mentions a physical space or facility, the venue information document should be included. While the query doesn't explicitly mention a physical space, the act of attending these events would require the venue's facilities, such as seating, sound systems, or restrooms. Therefore, including the venue information document ensures that the next node can verify if the venue can accommodate such events and provide relevant details about the physical spaces available. </think> { "reasoning": "The query asks about upcoming cultural performances, which are covered in the 'upcoming events' document. However, the venue information document is required to confirm the physical spaces and facilities that can host these events. Including the venue document ensures the response addresses both the event availability and the suitability of the venue's facilities.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming events such as live performances, theater productions, or creative workshops. The query directly relates to events, which are covered in the Upcoming Events Document. However, the guidelines state that if a query mentions a physical space or facility, the Venue Information Document should be included. The user's mention of "theater productions" implies the need to check if the venue has a suitable space for such activities. Since the Venue Information Document includes details about the venue's facilities and ambiance, it is necessary to include it to confirm the availability and suitability of the space. This ensures the response is accurate and avoids potential issues where the venue cannot accommodate the event. </think> { "reasoning": "The query asks about upcoming events like live performances, theater productions, or creative workshops. While the Upcoming Events Document handles event details, the mention of 'theater productions' necessitates including the Venue Information Document. This ensures the next node can verify if the venue has a suitable physical space (e.g., theater facilities) and confirm ambiance, seating, and amenities that support such activities. Guidelines mandate inclusion when physical spaces are referenced, aligning with the need to validate suitability.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming performances, concerts, or art exhibitions this month. The query directly relates to events, which are covered in the upcoming events document. However, the guidelines specify that even if the main topic is handled by another document, mentioning a physical space or facility requires including the venue information document. Since the question involves events, which might require knowing the venue's capacity or facilities, the venue document is necessary to confirm if the space can accommodate such activities. Therefore, despite the crossover with the upcoming events document, the venue information document should be included to provide context on the venue's capacity and facilities. </think> { "reasoning": "The query asks about upcoming performances, concerts, or art exhibitions, which fall under the upcoming events document. However, the venue information document is necessary to confirm the venue's capacity and facilities, which are essential for determining suitability. This aligns with the guideline that mentions of physical spaces or facilities require inclusion of the venue information document, even if the core answer resides in another document.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming theater productions, art shows, or business seminars. The venue information document is necessary to confirm if the venue has the physical space and facilities suitable for such events. Even though the query pertains to events, the guidelines state that any mention of a physical space or facility requires including the venue document. This ensures the next node can verify the venue's capacity and amenities, which are crucial for determining suitability. The crossover topics, like events, are handled by another document, but the physical space's existence and attributes are in the venue document. Therefore, including it is essential for a comprehensive response. </think> { "reasoning": "The query asks about upcoming theater productions, art shows, or business seminars. While these events are covered in the upcoming events document, the venue information document is required to confirm the physical space and facilities suitable for such activities. The guidelines mandate inclusion when physical spaces or facilities are mentioned, ensuring the response accounts for the venue's capacity and amenities.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming plans for concerts, art exhibitions, or theater performances. The query pertains to events, which are covered by the upcoming events document. However, the guidelines specify that if the query involves hosting an activity at the venue, the venue information document should be included. The reasoning is that the venue document provides details on facilities like seating capacity, ambiance, and amenities, which are crucial for assessing suitability for such events. Even though the main answer is in the upcoming events document, the venue document is necessary to confirm the venue's capacity and facilities for hosting these events. Thus, including the venue information document is essential for a comprehensive response. </think> { "reasoning": "The query asks about upcoming events, which are covered by the upcoming events document. However, the venue information document is required to confirm the venue's capacity, facilities, and ambiance, which are critical for assessing suitability for hosting these events. This aligns with the guideline that queries involving activities at the venue necessitate including the venue document to ensure accurate context.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming live performances, art installations, or business conferences. The venue information document does not cover events, as those are handled by the upcoming events document. However, the guidelines specify that if the query mentions an activity requiring space or facilities, the venue document should be included. Since hosting such events would require checking the venue's facilities, the decision is to include the venue information document to ensure the next node can verify if the space and amenities are suitable for the events. </think> { "reasoning": "The query asks about hosting live performances, art installations, or business conferences, which are events. The venue information document does not cover events, as that is handled by the upcoming events document. However, the guidelines state that any mention of activities requiring space or facilities necessitates including the venue document. This ensures the next node can verify if the venue's physical space and amenities are suitable for the events, aligning with the need to fact-check assumptions about the venue's capabilities.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming events like live performances, art exhibits, or interactive workshops. This query primarily relates to events, which are covered by the Upcoming Events document. However, the guidelines state that if the query mentions a physical space or facility, the Venue Information document should be included. The mention of 'interactive workshops' implies the need to check if the venue has the appropriate space and facilities to host such events. Even though the core answer is in the Upcoming Events document, the Venue Information is necessary to confirm the venue's capacity, amenities, and suitability for hosting these events. Therefore, including the Venue Information document ensures a comprehensive response, addressing both the event details and the physical space requirements. </think> { "reasoning": "The query asks about upcoming events like live performances, art exhibits, or interactive workshops. While the Upcoming Events document covers event specifics, the Venue Information document is required to confirm the venue's capacity, facilities, and suitability for hosting these activities. This ensures the response accounts for the physical space and amenities needed to accommodate such events.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming plans for live music, theater, or seminars. The venue information document is crucial here because it contains details about the venue's facilities, such as sound systems, seating capacity, and amenities that are essential for hosting events. Even though the upcoming events are covered in a separate document, the venue information is necessary to confirm the physical space's suitability for these activities. Additionally, the guidelines state that any mention of activities at the venue necessitates including the venue information document. Therefore, the decision is to include the venue information document to ensure the response accounts for the venue's capabilities and policies. </think> { "reasoning": "The query asks about upcoming plans for live music, theater, or seminars, which relate to the venue's facilities and capacity. The venue information document includes details about sound systems, seating layout, and amenities, which are critical for determining if the venue can accommodate such activities. Even though the upcoming events are covered in a separate document, the venue information is necessary to confirm the physical space's suitability. The guidelines also mandate including the venue information document when activities like live music or seminars are mentioned, as it provides context for the venue's capabilities.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming art exhibitions, live performances, or charity events happening at the venue. The query relates to events, which are covered in the Upcoming Events Document. However, the guidelines state that any mention of activities or events requiring space should include the Venue Information Document. Since the user's query involves potential events, the Venue Information Document is necessary to verify if the venue has the facilities to host such events. Additionally, the guidelines emphasize including the Venue Information Document for any mention of activities or events, even if the core of the query is about the events themselves. Therefore, despite the Upcoming Events Document being the primary source, the Venue Information Document is still required to ensure the venue's physical space and facilities are considered. </think> { "reasoning": "The query asks about upcoming events, which are covered in the Upcoming Events Document. However, the mention of events implies a need to verify if the venue has the physical space and facilities to accommodate these activities. The Venue Information Document contains details about the venue's facilities, seating capacity, and policies, which are essential for determining suitability. Including it ensures the response accounts for the venue's capabilities, aligning with the guideline to include the Venue Information Document for activities requiring space.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about special plans for concerts, theater performances, or business dinners this month. The query primarily relates to upcoming events, which falls under the Upcoming Events Document. However, the guidelines specify that if the query mentions any physical space or facility, the Venue Information Document must be included. The mention of 'concerts' and 'theater performances' implies the need to verify if the venue has suitable spaces for these events. The Venue Information Document contains details about the venue's facilities, seating capacity, and amenities, which are crucial for determining if the venue can host such activities. Even though the core answer lies in the Upcoming Events Document, the Venue Information Document is necessary to confirm the physical space and related policies, ensuring the response is accurate and comprehensive. </think> { "reasoning": "The query asks about special plans for concerts, theater performances, or business dinners, which are event-related. While the Upcoming Events Document handles event specifics, the Venue Information Document is required to verify if the venue has suitable spaces (e.g., theater seating, sound systems) for these activities. Including the Venue Information Document ensures the response accounts for physical space constraints and amenities, enhancing accuracy and relevance.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about events involving music concerts, art shows, or theater performances. The query falls under the upcoming events document, which covers event details. However, the guidelines specify that if a query involves an activity (like hosting events) and mentions a physical space, the venue information document should be included. Even though the query is about events, the next node needs to confirm if the venue has the necessary facilities, such as sound systems or seating capacity, to host these events. Therefore, the venue information document is relevant to ensure the venue can accommodate such activities. </think> { "reasoning": "The query asks about events involving music concerts, art shows, or theater performances. While the upcoming events document contains details about these events, the venue information document is required to confirm if the venue has the necessary facilities (e.g., sound systems, seating capacity) to host such activities. Including the venue information ensures the response accounts for the physical space and amenities required for these events.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming live performances, music concerts, or art exhibitions. The query directly relates to events, which are covered in the Upcoming Events document. However, the guidelines state that any mention of activities at the venue necessitates including the Venue Information document. Since the user is asking about events, the Venue Information is needed to confirm the venue's facilities and capacity, which are essential for hosting such activities. The guidelines emphasize including the Venue Information when activities are mentioned, even if the core answer is in another document. Thus, the decision is to include the Venue Information document. </think> { "reasoning": "The user's query about upcoming live performances, music concerts, or art exhibitions requires information about the venue's facilities and capacity. The Venue Information document contains details about the venue's physical spaces, amenities, and policies, which are crucial for determining if the venue can host such events. While the Upcoming Events document covers event specifics, the Venue Information is necessary to confirm the venue's suitability for hosting these activities.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming theater performances, live music events, or art shows. The query directly relates to events, which are covered in the Upcoming Events Document. However, the guidelines specify that if the query mentions a physical space or facility, the Venue Information Document should be included. Since the query refers to events happening in the venue's spaces, the Venue Information Document is necessary to confirm the availability of the physical areas where these events would occur. Therefore, even though the core answer is in the Upcoming Events Document, the Venue Information Document is required to verify the venue's facilities and spaces, ensuring the response is accurate and comprehensive. </think> { "reasoning": "The query asks about upcoming theater performances, live music events, or art shows, which are covered by the Upcoming Events Document. However, the mention of 'the near future' implies the need to verify the venue's facilities and physical spaces to ensure they can accommodate such activities. The Venue Information Document provides critical details about the venue's physical spaces, facilities, and policies, which are essential for confirming suitability. Thus, including the Venue Information Document ensures the response is accurate and comprehensive.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming events like concerts, theater productions, or creative workshops. The query does not mention specific physical spaces, but it pertains to events, which are covered in the Upcoming Events Document. However, the guidelines state that any mention of activities requiring space (like workshops) necessitates including the Venue Information Document to assess available facilities. Since the user is asking about events that might require the venue's facilities, the Venue Information Document should be included to ensure the next node can confirm suitability based on available spaces and amenities. </think> { "reasoning": "The query asks about events requiring the venue's facilities (e.g., space for workshops), which are detailed in the Venue Information Document. While events themselves are covered in the Upcoming Events Document, the venue's physical space and amenities are critical for determining suitability. Including the Venue Information Document ensures the next node can verify if the venue can accommodate such activities, aligning with the guideline that queries about activities necessitate venue context.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming events, live performances, or art installations. According to the guidelines, the venue information document should be excluded since the query relates to upcoming events, which are covered by the upcoming events document. However, the guidelines also state that if a query mentions a physical space or facility, the venue document should be included. The mention of events implies the need to verify if the venue has the necessary facilities, such as a stage or space, which is covered in the venue information document. Therefore, even though the main answer is in the upcoming events document, the venue document is needed to confirm the physical space's availability for such activities. This aligns with the rule that any mention of activities at the venue requires including the venue document to ensure suitability and accommodate the customer's request. </think> { "reasoning": "The query asks about upcoming events, which are covered in the upcoming events document. However, the mention of events implies a need to verify if the venue has the necessary facilities, such as a stage or space, which is covered in the venue information document. Including this document ensures the next node can confirm suitability and accommodate the customer's request.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about scheduled events featuring theater performances, art exhibits, or music festivals. The query specifically asks about upcoming events, which falls under the Upcoming Events Document. However, the guidelines state that even if the crux of the query is about events, mentioning a physical space or facility (like a theater or art exhibit area) necessitates including the Venue Information Document. Since the user is asking about events in these areas, the Venue Information Document is required to confirm the existence and details of these spaces. Additionally, the Venue Information Document provides context on facilities like sound systems, seating capacity, and ambiance, which are relevant for hosting such events. Therefore, despite the query being about events, the Venue Information Document is necessary to ensure the venue's physical capabilities support these activities. </think> { "reasoning": "The query asks about scheduled events featuring theater performances, art exhibits, or music festivals. While these events are covered by the Upcoming Events Document, the mention of 'theater performances' and 'art exhibits' relates to the venue's physical spaces (theater and art exhibits). The Venue Information Document contains details about facilities, seating capacity, and ambiance, which are crucial for confirming whether these spaces exist and can accommodate such events. Including this document ensures the next node can verify suitability and provide comprehensive information.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming performances, concerts, or art events. The venue information document does not cover events, as that is handled by the upcoming events document. However, the guidelines state that if a query involves activities or events, the venue document should be included to check if the venue's facilities can accommodate such activities. Since the query is about scheduled events, the venue document is needed to confirm the physical space and facilities, even though the events themselves are covered elsewhere. Thus, including the venue document ensures the next node can verify if the venue can host the events mentioned in the query. </think> { "reasoning": "The query asks about upcoming performances, concerts, or art events, which are covered by the upcoming events document. However, the venue information document is necessary to verify if the venue's physical space and facilities can accommodate such events. The guidelines mandate inclusion when activities or events are mentioned, as the venue document provides critical context about the venue's capabilities.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about live performances, musical showcases, or art festivals for this month. The venue information document doesn't cover events, which are handled by the upcoming events document. However, the guidelines state that any mention of activities requiring physical space necessitates including the venue document. Since the query involves planned events, the venue document is needed to confirm availability of suitable spaces, like a theater or bar, which are physical facilities. This ensures the response accounts for the venue's capacity and amenities, aligning with the guidelines. </think> { "reasoning": "The query asks about planned events, which are covered in the upcoming events document. However, the mention of 'live performances' and 'art festivals' relates to the venue's physical spaces and facilities. The venue information document is necessary to verify if the venue has suitable areas like a theater or bar for these activities, ensuring the response accounts for physical space constraints. This aligns with the guideline that queries mentioning activities requiring physical space necessitate including the venue document.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming theater productions, musical performances, or workshops. The query focuses on events, which are covered in the upcoming events document. However, the guidelines state that if a query mentions a physical space or facility, the venue information document should be included. Since theater, musical performances, and workshops are physical spaces within the venue, the venue document is necessary to confirm their availability and facilities. Even though the core answer is in the upcoming events document, the venue document is still required to verify the existence of these spaces and their amenities. Therefore, the decision is to include the venue information document. </think> { "reasoning": "The query asks about upcoming theater productions, musical performances, or workshops. While the core answer lies in the upcoming events document, the venue information document is needed to confirm the existence of these physical spaces and their facilities. The guidelines mandate inclusion when a query mentions a physical space or facility, ensuring the next node can verify suitability and provide accurate context.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about performances, workshops, or cultural events at the venue. The query directly relates to events, which are covered in the upcoming events document. However, the guidelines specify that if a query involves activities at the venue, the venue information document should be included to confirm if the physical space can accommodate such events. Since the query is about events, the upcoming events document is the primary source. However, the venue information is needed to verify if the venue can host these activities. Therefore, the venue information document should be included to ensure the next node can address both the availability of events and the suitability of the venue's physical space. </think> { "reasoning": "The query asks about performances, workshops, or cultural events, which are covered in the upcoming events document. However, the venue information document is required to verify if the venue can accommodate these activities, ensuring the next node can provide a comprehensive response about both event availability and venue suitability.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The query asks about live music performances, art exhibits, or theater shows. These are events, which fall under the Upcoming Events Document. However, the guidelines state that any mention of activities requiring physical space should include the Venue Information Document. Since these events would likely use the venue's facilities, the document is needed to confirm availability and suitability. Thus, even though the main answer is in the Upcoming Events Document, the Venue Information Document is still relevant for context. </think> { "reasoning": "The query about live music performances, art exhibits, or theater shows pertains to events, which are covered in the Upcoming Events Document. However, the guidelines specify that any mention of activities requiring physical space necessitates including the Venue Information Document. This ensures the next node can verify if the venue's facilities (e.g., sound system, seating capacity) are suitable for these events, even though the core answer resides in the Upcoming Events Document.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming concerts, theater productions, or cultural events. The venue information document does not contain event details, which are covered by the upcoming events document. However, the guidelines state that if the query mentions a physical space or facility, the venue document should be included. Since the query refers to events, the venue document is not directly relevant. However, the user's mention of events implies the need to check if the venue has the necessary facilities, such as a stage or seating capacity. Therefore, the venue document should be included to ensure the next node can verify if the venue can accommodate such events. </think> { "reasoning": "The query asks about upcoming events, which are covered by the upcoming events document. However, the mention of 'concerts, theater productions, or cultural events' implies the need to check the venue's facilities and capacity. The venue information document is necessary to confirm if the venue can host such events, as it contains details about the physical space, seating, and amenities. This aligns with the guideline that mentions of activities requiring physical space necessitate including the venue document.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about hosting live performances, art exhibitions, or corporate conferences. The query primarily relates to events and their logistics. The venue information document contains details about facilities, seating capacity, and amenities, which are crucial for hosting events. Since the query involves physical spaces and activities, the venue document is necessary to confirm suitability and provide relevant context. The guidelines emphasize including the venue document when activities or events are mentioned, ensuring the next node can assess the venue's capabilities. The crossover topics do not cover event logistics, so the venue document is essential here. </think> { "reasoning": "The query asks about hosting live performances, art exhibitions, or corporate conferences, which require checking the venue's physical spaces, facilities, and policies. The venue information document contains details about seating capacity, amenities, and facilities, which are essential for determining suitability. Guidelines mandate inclusion when activities or events are mentioned, as the next node needs context to assess feasibility.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> Okay, let's break this down. The user is asking about art exhibitions, musical performances, or business workshops. First, I need to check if the venue information document is relevant here. The query mentions "art exhibitions," "musical performances," and "business workshops." These are events, which according to the guidelines, are covered by the upcoming events document. The venue information document doesn't handle event details. However, the guidelines also state that if the query involves activities that require checking the venue's physical space, the venue document should be included. Even though the main answer would come from the upcoming events document, the next node might need to confirm if the venue can accommodate these events. For instance, if the venue has a suitable space for workshops or performances, the answer would benefit from knowing the facilities. The venue document includes information on seating capacity, facilities like projectors, sound systems, and ambiance, which are crucial for determining suitability. Additionally, the guidelines mention that any activity-related queries require the venue document to check the physical space. Since the user is asking about events, which involve using the venue's facilities, including the venue information ensures the next node can address both the event details and the venue's capabilities. Therefore, the decision is to include the venue information document. </think> { "reasoning": "The query asks about upcoming art exhibitions, musical performances, or business workshops. While event details are covered in the upcoming events document, the venue information document is required to confirm the physical space's suitability for these activities. The venue document contains details about seating capacity, facilities (e.g., projectors, sound systems), and ambiance, which are critical for determining if the venue can accommodate these events. Additionally, the guidelines explicitly state that queries involving activities requiring the venue's physical space or facilities necessitate inclusion of the venue information document.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about planned live events, such as music performances, art exhibits, or workshops. The query falls under the 'Upcoming Events Document' as it pertains to specific events. However, the guidelines state that if the query involves activities that require the venue's physical space or facilities, the venue information document should be included. Since live events would likely require space and facilities like sound systems or projectors, the venue document is necessary to confirm availability and suitability. Therefore, even though the main answer is in the events document, the venue document is still required to provide a comprehensive response. </think> { "reasoning": "The query asks about planned live events, which are covered in the Upcoming Events Document. However, the venue information document is required to confirm the venue's facilities and physical space, which are essential for hosting such events. This ensures the response accounts for the venue's capacity, amenities, and suitability for the activities described.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about corporate events, theater productions, or music festivals on the calendar. The venue information document does not contain event schedules, as those are covered in the upcoming events document. However, the guidelines state that any mention of activities requiring physical space necessitates including the venue document. Even though the query is about events, the venue's facilities and policies are crucial for determining if the venue can accommodate such activities. Therefore, the venue information document should be included to provide context on the physical space and policies that influence event suitability. </think> { "reasoning": "The query asks about upcoming corporate events, theater productions, or music festivals. While event schedules are covered in the upcoming events document, the venue information document is required to verify if the venue's physical space and facilities (e.g., seating capacity, amenities) are suitable for hosting these events. The guidelines mandate inclusion when activities require physical space, ensuring the response accounts for venue constraints.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming performances, exhibitions, or conferences. The venue information document does not cover events, as those are handled by the upcoming events document. However, the guidelines state that if a query mentions a physical space or facility, the venue document should be included. Since the user's query involves activities that require checking the venue's facilities and ambiance, the venue document is necessary to determine if suitable spaces exist. Therefore, despite the crossover topic, the venue document is relevant for context. </think> { "reasoning": "The query asks about upcoming performances, exhibitions, or conferences, which are covered in the upcoming events document. However, the guidelines specify that if a query involves activities requiring the venue's physical space or facilities, the venue information document must be included. This ensures the next node can verify if the venue can accommodate such activities and provide relevant details about its ambiance and amenities.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming events such as art exhibitions, live performances, or corporate events. The venue information document is relevant here because it provides details about the venue's facilities, which are necessary to determine if the venue can host these events. Even though the query is about events, the venue document is needed to confirm the physical space and amenities that support such activities. This aligns with the guideline that mentions of physical spaces or facilities require inclusion of the venue document, as it ensures the next node can verify suitability for the events. </think> { "reasoning": "The query asks about upcoming events like art exhibitions, live performances, or corporate events. The venue information document is necessary to confirm the physical space and facilities (e.g., seating, amenities, capacity) that can accommodate these activities. Even though events are typically covered by the upcoming events document, the venue document is required to validate the venue's suitability for hosting such events, aligning with the guideline that mentions of physical spaces or facilities necessitate inclusion.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about theater productions, art exhibits, or live concerts soon. The query relates to upcoming events, which are covered in the Upcoming Events Document. However, the Venue Information Document is required to confirm the existence of these facilities. The guidelines state that any mention of a physical space or activity necessitates including the Venue Information Document. Since the query involves hosting events, the Venue Information Document is necessary to verify the venue's capacity and facilities for such activities. Therefore, the decision is to include the Venue Information Document. </think> { "reasoning": "The query asks about upcoming theater productions, art exhibits, or live concerts, which are categorized under the Upcoming Events Document. However, the Venue Information Document is required to verify the existence of the facilities (e.g., theater, art gallery, stage) and their capacity. The guidelines mandate inclusion when physical spaces or activities are mentioned, ensuring the venue can accommodate these events.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is asking about upcoming live performances, art shows, or business events. The query relates to events, which are covered in the Upcoming Events Document. However, the guidelines specify that if the query mentions a physical space or facility, the Venue Information Document should be included. Since events typically occur in specific areas like the theatre or bar, the Venue Information Document is necessary to confirm the existence and details of those spaces. Additionally, the Venue Information Document contains policies and amenities that might affect event suitability, such as seating capacity or facilities. Therefore, even though the core answer is in the Upcoming Events Document, the Venue Information Document is required to provide a comprehensive response, ensuring the next node can verify the venue's capabilities for the events mentioned. </think> { "reasoning": "The query asks about upcoming live performances, art shows, or business events. While these topics are covered in the Upcoming Events Document, the Venue Information Document is required to confirm the existence and details of physical spaces like the theatre or bar, which are essential for event suitability. The Venue Information Document also provides context on facilities and policies that may impact event logistics, ensuring a comprehensive response.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> Okay, let's tackle this query. The user is asking if there are any major exhibitions, performances, or conferences scheduled for the next few weeks. First, I need to determine which document would contain the necessary information. The venue information document covers physical aspects like facilities, seating, policies, etc. But the query is about upcoming events. According to the guidelines, events are handled by the Upcoming Events document. However, the guidelines also state that if the query mentions a physical space or facility, the venue document should be included. The user's query doesn't explicitly mention a physical space, but events like exhibitions or conferences might require checking if the venue has suitable facilities. For example, a conference might need a specific space, like a theatre or a large area. The venue document includes details on facilities and seating capacity, which could help determine if the venue can accommodate such events. Even though the main answer about events is in the Upcoming Events document, including the venue info ensures the next node can verify if the venue's facilities are appropriate. This prevents situations where an event is scheduled but the venue can't handle it due to physical constraints. Therefore, the venue information document should be included to provide context on facilities and capacity. </think> { "reasoning": "The query asks about upcoming exhibitions, performances, or conferences, which fall under the scope of the Upcoming Events document. However, the venue information document is still relevant because the next node may need to verify if the venue has the necessary facilities (e.g., a suitable space, seating capacity, or amenities like projectors) to accommodate such events. Including the venue document ensures the response accounts for physical constraints and suitability, even though the core answer resides elsewhere.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming live performances, art exhibits, or business meetings. The query primarily relates to events, which are covered in the Upcoming Events Document. However, the guidelines state that any mention of activities requiring physical space or facilities necessitates including the Venue Information Document. Even though the main topic is events, the need to confirm the venue's capacity, amenities, and suitability for hosting such activities means the Venue Information Document is relevant. This ensures the next node can verify if the venue can accommodate these events and provide a comprehensive response. </think> { "reasoning": "The query asks about live performances, art exhibits, or business meetings, which are events. While these are covered in the Upcoming Events Document, the mention of activities requiring physical space or facilities necessitates including the Venue Information Document. This ensures the next node can verify if the venue has the necessary capacity, amenities, and suitability for hosting these events, aligning with the guideline that queries involving activities at the venue require inclusion of the Venue Information Document.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming music concerts, theater productions, or corporate seminars. The query focuses on events, which are covered by the Upcoming Events Document. However, the guidelines state that if the query mentions any physical space or facility, the Venue Information Document should be included. The user's question does not explicitly mention a physical space, but the need to check if the venue can accommodate these events is crucial. Since the Venue Information Document includes details about facilities, seating capacity, and ambiance, it is necessary to include it to ensure the venue can host such events. This aligns with the guideline to include the Venue Information Document when there's a risk of the response being incomplete without it. </think> { "reasoning": "The query asks about upcoming events (music concerts, theater productions, corporate seminars), which are covered by the Upcoming Events Document. However, the Venue Information Document is necessary to confirm if the venue has the physical space, facilities, and amenities to host these events. This ensures the response accounts for the venue's capacity, layout, and suitability for the requested activities, aligning with the guideline to include the Venue Information Document for queries involving activities requiring physical space.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming plans for theater performances, music festivals, or art exhibitions. This query relates to events, which are covered in the Upcoming Events Document. However, the guidelines state that even if the core answer is in another document, mentioning physical spaces or facilities requires including the Venue Information Document. The Venue Information Document contains details about the venue's physical spaces, which are necessary to confirm if the venue can host such events. Additionally, the query implies the need to assess the venue's capacity and facilities, which are part of the Venue Information Document. Therefore, despite the Upcoming Events Document handling event specifics, the Venue Information Document is essential to verify the venue's suitability for hosting these events. </think> { "reasoning": "The query asks about upcoming theater performances, music festivals, or art exhibitions, which are covered in the Upcoming Events Document. However, the mention of hosting these events implies the need to verify the venue's physical spaces and facilities, as outlined in the Venue Information Document. This ensures the venue can accommodate the activities and provides context about its capacity and amenities. Including the Venue Information Document is necessary to fact-check the venue's suitability for hosting such events.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about upcoming performances, art shows, or conferences at the venue. The venue information document does not cover events, which are handled by the upcoming events document. However, the query involves activities that require the venue's facilities and space. Since the user might need to know if the venue has suitable spaces for these events, the venue information document is relevant. It provides details on the physical space, amenities, and policies that could influence whether the venue can host such activities. Therefore, including the venue information document is necessary to ensure the response is accurate and comprehensive. </think> { "reasoning": "The query asks about upcoming performances, art shows, or conferences, which are covered by the upcoming events document. However, the venue information document is needed to confirm if the venue's physical space, facilities, and policies (e.g., seating capacity, amenities, rules) are suitable for hosting such events. This ensures the response considers the venue's capabilities and avoids assumptions.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about theater performances, workshops, or cultural events on the schedule. The venue information document does not contain event details, as those are covered by the upcoming events document. However, the guidelines state that if the query mentions a physical space or facility, the venue document should be included. Since theater performances and workshops involve the venue's physical space and facilities, the venue information is necessary to confirm if such activities are possible. Therefore, even though the events themselves are in another document, the venue document is required to verify the existence of the necessary facilities and space. This aligns with the guideline to include the venue document when physical spaces are mentioned, even if the main topic is handled elsewhere. </think> { "reasoning": "The query asks about theater performances, workshops, or cultural events, which fall under the upcoming events document. However, the venue information document is required to confirm the existence of the physical spaces and facilities needed for such activities, such as seating capacity, sound systems, and restrooms. This aligns with the guideline to include the venue document when physical spaces or facilities are mentioned, even if the core answer lies elsewhere.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The query asks about upcoming exhibitions, live performances, or professional events. These are covered in the Upcoming Events document, which is a crossover topic. However, the guidelines state that if the query mentions any physical space or facility, the venue information document should be included. The mention of 'events' implies a need to check if the venue has the facilities to host such activities. Even though the events are in another document, the venue information is required to confirm the physical space and amenities, ensuring the response is accurate and avoids scenarios where the venue cannot accommodate the event. Therefore, including the venue information document is necessary to provide a comprehensive answer. </think> { "reasoning": "The query asks about upcoming events, which are handled by the Upcoming Events document. However, the mention of 'events' implies a need to check the venue's physical space and facilities. The venue information document contains details about the venue's spaces, amenities, and policies, which are essential to confirm suitability for hosting events. Including the venue information ensures the response accounts for the venue's capacity and facilities, avoiding scenarios where the venue cannot accommodate the event.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is inquiring about performances, art shows, or business conferences the venue has in store. The query relates to events, which are typically covered by the upcoming events document. However, the guidelines state that if the query mentions an activity that requires checking the venue's physical space or facilities, the venue information document should be included. Since the user is asking about events, the venue's facilities and capacity are crucial to determine if they can accommodate such activities. Therefore, the venue information document is necessary to provide context on the venue's spaces and amenities, ensuring the response is accurate and comprehensive. </think> { "reasoning": "The query asks about performances, art shows, or business conferences, which are events. While the upcoming events document covers these details, the venue information document is needed to verify the venue's physical spaces and facilities. The guidelines mandate including the venue document when activities require checking suitability of the venue's infrastructure, ensuring accurate responses about space availability and suitability.", "decision": "include" } <\|im_end\|>
<\|im_start\|>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 ### <\|im_end\|> <\|im_start\|>user Look at the following query: ### QUERY ### include ### 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. <\|im_end\|> <\|im_start\|>assistant <think> The user is asking about upcoming music concerts, theater performances, or interactive art exhibits. These are events, which fall under the upcoming events document. However, the venue information document is necessary to confirm if the venue can accommodate these activities. The guidelines state that any mention of activities requiring space should include the venue document. Since the query involves events, the venue info is still relevant for confirming physical space and facilities. </think> { "reasoning": "The query asks about upcoming events, which are covered by the upcoming events document. However, the venue information document is required to verify if the venue has the necessary physical space and facilities to host such events. This ensures the next node can confirm suitability and provide accurate information.", "decision": "include" } <\|im_end\|>

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.