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|>
|
End of preview. Expand
in Data Studio
README.md exists but content is empty.
- Downloads last month
- 2