text
stringlengths 7.78k
10.6k
|
|---|
<|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 upcoming events document 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 in the upcoming events document:
### UPCOMING EVENTS DOCUMENT CONTENTS ###
There are only 3 types of information and they refer to:
- 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.
-The special one-off events are usually events for special occasions like a business aniversary, New Year's Eve, Christmas, etc.
-One off experiences like a tasting workshop, a live music event, a comedy night, will also be listed here If planned by the venue.
If there are no upcoming events, then the document will be empty.
DO NOT ASSUME ANY OTHER INFORMATION OTHER THAN THE LISTED ABOVE IS IN THE UPCOMING EVENTS DOCUMENT. IF THE QUERY HAS NOTHING TO DO WITH THE ABOVE CONTENTS, THE UPCOMING EVENTS DOCUMENT SHOULD BE EXCLUDED FROM THE CONTEXT.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
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 upcoming events document in your 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 ###
Do you provide group booking or private event packages?
### 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 UPCOMING EVENTS DOCUMENT ###
ALL QUERIES HANDLED SOLELY BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE UPCOMING EVENTS DOCUMENT FROM THE CONTEXT. THESE DOCUMENTS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS 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.
### RESERVATIONS DOCUMENT CONTENTS ###
- 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.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
### MENU DOCUMENT CONTENTS ###
- 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 ###
- 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.
AGAIN ALL THE DOCUMENTS IN THE CROSSOVER TOPICS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS DOCUMENT.
### GUIDELINES ###
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude. This logic also extends to product promotions, happy hours, and special offers.
If The upcoming events document should be included in the context if the query is related to obtaining information about events, special plans, or updates about future activities at the venue.
This logic however will not stretch to queries about booking a table for an event, as this would be handled by the reservations document. The upcoming events document is only for queries about the events themselves.
Also private events and space rentals are not covered in the upcoming events document. These are handled by the reservations document. The upcoming events document only handles events that are open to the public.
If the query is about plans for the next month, the upcoming events document should be included to provide context about the monthly events that the user might be interested in. Even if the core of the query lies elswhere, the upcoming events document will still be useful for the next node in this particular scenario as they can use this information to suggest alternatives to the customer or entice them with the upcming event information.
If the query does not relate to the upcoming events or plans for the coming week, month or ask about one-off events reply "exclude" in the decision field.
<|im_end|>
<|im_start|>assistant
<think>
Okay, let me break this down. The user is asking about group booking or private event packages.
First, I need to check what each document covers. The upcoming events document includes special one-off events, weekly/monthly events, and their details like dates and tickets. But the question here is about group bookings and private events.
Looking at the crossover topics, the reservations document specifically handles group bookings and how they're managed. It covers policies, minimum spends, and how to make reservations for groups. Private events and space rentals also fall under the reservations document, not the upcoming events. The upcoming events are public, not private.
The query isn't about existing public events but about booking packages for groups or private events. So the reservations document is the right place. Therefore, the upcoming events document doesn't contain relevant info here. Excluding it makes sense to avoid unnecessary context.
</think>
{
"reasoning": "The query about group bookings or private event packages relates to reservation policies and handling of large bookings, which are covered in the reservations document. The upcoming events document focuses on publicly available events (e.g., live music, workshops) rather than private event logistics or group booking policies. Since the query pertains to venue booking services rather than event attendance, the upcoming events document is not relevant and should be excluded.",
"decision": "exclude"
}
<|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 upcoming events document 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 in the upcoming events document:
### UPCOMING EVENTS DOCUMENT CONTENTS ###
There are only 3 types of information and they refer to:
- 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.
-The special one-off events are usually events for special occasions like a business aniversary, New Year's Eve, Christmas, etc.
-One off experiences like a tasting workshop, a live music event, a comedy night, will also be listed here If planned by the venue.
If there are no upcoming events, then the document will be empty.
DO NOT ASSUME ANY OTHER INFORMATION OTHER THAN THE LISTED ABOVE IS IN THE UPCOMING EVENTS DOCUMENT. IF THE QUERY HAS NOTHING TO DO WITH THE ABOVE CONTENTS, THE UPCOMING EVENTS DOCUMENT SHOULD BE EXCLUDED FROM THE CONTEXT.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
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 upcoming events document in your 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 ###
Can I book a private event or group reservation with a special package?
### 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 UPCOMING EVENTS DOCUMENT ###
ALL QUERIES HANDLED SOLELY BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE UPCOMING EVENTS DOCUMENT FROM THE CONTEXT. THESE DOCUMENTS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS 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.
### RESERVATIONS DOCUMENT CONTENTS ###
- 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.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
### MENU DOCUMENT CONTENTS ###
- 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 ###
- 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.
AGAIN ALL THE DOCUMENTS IN THE CROSSOVER TOPICS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS DOCUMENT.
### GUIDELINES ###
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude. This logic also extends to product promotions, happy hours, and special offers.
If The upcoming events document should be included in the context if the query is related to obtaining information about events, special plans, or updates about future activities at the venue.
This logic however will not stretch to queries about booking a table for an event, as this would be handled by the reservations document. The upcoming events document is only for queries about the events themselves.
Also private events and space rentals are not covered in the upcoming events document. These are handled by the reservations document. The upcoming events document only handles events that are open to the public.
If the query is about plans for the next month, the upcoming events document should be included to provide context about the monthly events that the user might be interested in. Even if the core of the query lies elswhere, the upcoming events document will still be useful for the next node in this particular scenario as they can use this information to suggest alternatives to the customer or entice them with the upcming event information.
If the query does not relate to the upcoming events or plans for the coming week, month or ask about one-off events reply "exclude" in the decision field.
<|im_end|>
<|im_start|>assistant
<think>
Okay, let's break down the user's query: "Can I book a private event or group reservation with a special package?"
First, I need to determine which document handles this type of request. The query is about booking a private event or group reservation, which involves reservations and possibly special packages. According to the crossover topics, the Reservations Document includes information on how groups and large bookings are handled, including policies and minimum spends.
Looking at the Upcoming Events Document contents, it covers public events like special one-offs, weekly, or monthly events, but private events and group reservations are explicitly mentioned as being handled by the Reservations Document. The Upcoming Events Document doesn't handle private bookings or reservations, only public events.
The user is asking about booking, which falls under the Reservations Document's responsibilities. Even though they mention a "special package," that likely refers to reservation packages, not public events. Therefore, the Upcoming Events Document isn't relevant here and should be excluded.
</think>
{
"reasoning": "The query asks about booking a private event or group reservation with a special package. This falls under group booking policies and reservation-related packages, which are explicitly covered by the reservations document. The upcoming events document does not handle private events or reservations, as it only lists public events (e.g., one-off, weekly, or monthly events) and their details. Since the query is about reservations and special packages for groups, the relevant context resides in the reservations document, not the upcoming events document.",
"decision": "exclude"
}
<|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 upcoming events document 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 in the upcoming events document:
### UPCOMING EVENTS DOCUMENT CONTENTS ###
There are only 3 types of information and they refer to:
- 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.
-The special one-off events are usually events for special occasions like a business aniversary, New Year's Eve, Christmas, etc.
-One off experiences like a tasting workshop, a live music event, a comedy night, will also be listed here If planned by the venue.
If there are no upcoming events, then the document will be empty.
DO NOT ASSUME ANY OTHER INFORMATION OTHER THAN THE LISTED ABOVE IS IN THE UPCOMING EVENTS DOCUMENT. IF THE QUERY HAS NOTHING TO DO WITH THE ABOVE CONTENTS, THE UPCOMING EVENTS DOCUMENT SHOULD BE EXCLUDED FROM THE CONTEXT.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
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 upcoming events document in your 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 ###
Do you offer any packages for group bookings or private events?
### 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 UPCOMING EVENTS DOCUMENT ###
ALL QUERIES HANDLED SOLELY BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE UPCOMING EVENTS DOCUMENT FROM THE CONTEXT. THESE DOCUMENTS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS 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.
### RESERVATIONS DOCUMENT CONTENTS ###
- 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.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
### MENU DOCUMENT CONTENTS ###
- 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 ###
- 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.
AGAIN ALL THE DOCUMENTS IN THE CROSSOVER TOPICS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS DOCUMENT.
### GUIDELINES ###
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude. This logic also extends to product promotions, happy hours, and special offers.
If The upcoming events document should be included in the context if the query is related to obtaining information about events, special plans, or updates about future activities at the venue.
This logic however will not stretch to queries about booking a table for an event, as this would be handled by the reservations document. The upcoming events document is only for queries about the events themselves.
Also private events and space rentals are not covered in the upcoming events document. These are handled by the reservations document. The upcoming events document only handles events that are open to the public.
If the query is about plans for the next month, the upcoming events document should be included to provide context about the monthly events that the user might be interested in. Even if the core of the query lies elswhere, the upcoming events document will still be useful for the next node in this particular scenario as they can use this information to suggest alternatives to the customer or entice them with the upcming event information.
If the query does not relate to the upcoming events or plans for the coming week, month or ask about one-off events reply "exclude" in the decision field.
<|im_end|>
<|im_start|>assistant
<think>
Okay, let's tackle this query. The user is asking, "Do you offer any packages for group bookings or private events?"
First, I need to figure out which document handles group bookings and private events. The Upcoming Events document mainly covers public events like one-off specials, weekly, or monthly happenings. But the user isn't asking about attending an event; they want to know about packages for their own group booking or private event.
Looking at the Crossover Topics, the Reservations document includes info on how groups and large bookings are handled, minimum spends for reserved areas, and policies around that. Private events and space rentals fall under Reservations, not Upcoming Events. The Venue Information document might have details on capacity or facilities, but the question is about packages, which are likely part of the reservation policies.
The guidelines mention that private events and space rentals are handled by the Reservations document. Since the query is about group bookings or private events packages, the answer would be in Reservations, not Upcoming Events. Therefore, the Upcoming Events document isn't relevant here. The decision should be to exclude it.
</think>
{
"reasoning": "The query asks about packages for group bookings or private events, which pertain to reservation policies and venue capacity. Such information is covered in the reservations document, specifically detailing group handling, minimum spends, and reservation policies. The upcoming events document does not contain information on private event packages or group booking policies, as it focuses on public events like one-off specials or weekly/monthly activities. Therefore, the upcoming events document is not relevant to answering this query.",
"decision": "exclude"
}
<|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 upcoming events document 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 in the upcoming events document:
### UPCOMING EVENTS DOCUMENT CONTENTS ###
There are only 3 types of information and they refer to:
- 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.
-The special one-off events are usually events for special occasions like a business aniversary, New Year's Eve, Christmas, etc.
-One off experiences like a tasting workshop, a live music event, a comedy night, will also be listed here If planned by the venue.
If there are no upcoming events, then the document will be empty.
DO NOT ASSUME ANY OTHER INFORMATION OTHER THAN THE LISTED ABOVE IS IN THE UPCOMING EVENTS DOCUMENT. IF THE QUERY HAS NOTHING TO DO WITH THE ABOVE CONTENTS, THE UPCOMING EVENTS DOCUMENT SHOULD BE EXCLUDED FROM THE CONTEXT.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
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 upcoming events document in your 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 ###
Are there group booking or private event packages available?
### 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 UPCOMING EVENTS DOCUMENT ###
ALL QUERIES HANDLED SOLELY BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE UPCOMING EVENTS DOCUMENT FROM THE CONTEXT. THESE DOCUMENTS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS 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.
### RESERVATIONS DOCUMENT CONTENTS ###
- 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.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
### MENU DOCUMENT CONTENTS ###
- 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 ###
- 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.
AGAIN ALL THE DOCUMENTS IN THE CROSSOVER TOPICS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS DOCUMENT.
### GUIDELINES ###
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude. This logic also extends to product promotions, happy hours, and special offers.
If The upcoming events document should be included in the context if the query is related to obtaining information about events, special plans, or updates about future activities at the venue.
This logic however will not stretch to queries about booking a table for an event, as this would be handled by the reservations document. The upcoming events document is only for queries about the events themselves.
Also private events and space rentals are not covered in the upcoming events document. These are handled by the reservations document. The upcoming events document only handles events that are open to the public.
If the query is about plans for the next month, the upcoming events document should be included to provide context about the monthly events that the user might be interested in. Even if the core of the query lies elswhere, the upcoming events document will still be useful for the next node in this particular scenario as they can use this information to suggest alternatives to the customer or entice them with the upcming event information.
If the query does not relate to the upcoming events or plans for the coming week, month or ask about one-off events reply "exclude" in the decision field.
<|im_end|>
<|im_start|>assistant
<think>
Okay, let's break this down. The user is asking about group booking or private event packages. First, I need to check what each document covers. The upcoming events document deals with public events like special occasions or weekly/monthly happenings. The reservations document, on the other hand, includes info on how groups and large bookings are handled. Since the query is about group bookings and private events, which are part of the reservations document's scope, the upcoming events document isn't needed here. The key is that private events aren't listed in the upcoming events, so the answer would come from reservations. Therefore, exclude the events document.
</think>
{
"reasoning": "The query is about group bookings and private event packages, which are covered in the reservations document (handling group policies, booking processes, and reserved area details). The upcoming events document focuses on public events like one-off experiences, weekly/monthly activities, or special occasions. Private event packages and group booking logistics fall outside the scope of the events document, making it irrelevant for this specific request.",
"decision": "exclude"
}
<|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 upcoming events document 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 in the upcoming events document:
### UPCOMING EVENTS DOCUMENT CONTENTS ###
There are only 3 types of information and they refer to:
- 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.
-The special one-off events are usually events for special occasions like a business aniversary, New Year's Eve, Christmas, etc.
-One off experiences like a tasting workshop, a live music event, a comedy night, will also be listed here If planned by the venue.
If there are no upcoming events, then the document will be empty.
DO NOT ASSUME ANY OTHER INFORMATION OTHER THAN THE LISTED ABOVE IS IN THE UPCOMING EVENTS DOCUMENT. IF THE QUERY HAS NOTHING TO DO WITH THE ABOVE CONTENTS, THE UPCOMING EVENTS DOCUMENT SHOULD BE EXCLUDED FROM THE CONTEXT.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
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 upcoming events document in your 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 ###
Can I arrange a private event or group booking with a customized package?
### 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 UPCOMING EVENTS DOCUMENT ###
ALL QUERIES HANDLED SOLELY BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE UPCOMING EVENTS DOCUMENT FROM THE CONTEXT. THESE DOCUMENTS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS 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.
### RESERVATIONS DOCUMENT CONTENTS ###
- 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.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
### MENU DOCUMENT CONTENTS ###
- 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 ###
- 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.
AGAIN ALL THE DOCUMENTS IN THE CROSSOVER TOPICS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS DOCUMENT.
### GUIDELINES ###
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude. This logic also extends to product promotions, happy hours, and special offers.
If The upcoming events document should be included in the context if the query is related to obtaining information about events, special plans, or updates about future activities at the venue.
This logic however will not stretch to queries about booking a table for an event, as this would be handled by the reservations document. The upcoming events document is only for queries about the events themselves.
Also private events and space rentals are not covered in the upcoming events document. These are handled by the reservations document. The upcoming events document only handles events that are open to the public.
If the query is about plans for the next month, the upcoming events document should be included to provide context about the monthly events that the user might be interested in. Even if the core of the query lies elswhere, the upcoming events document will still be useful for the next node in this particular scenario as they can use this information to suggest alternatives to the customer or entice them with the upcming event information.
If the query does not relate to the upcoming events or plans for the coming week, month or ask about one-off events reply "exclude" in the decision field.
<|im_end|>
<|im_start|>assistant
<think>
Okay, let's tackle this query. The user is asking about arranging a private event or group booking with a customized package. First, I need to check what's in the upcoming events document. According to the guidelines, the events document includes special one-off events, weekly/monthly events, and their details like dates, tickets, and policies. Private events and group bookings aren't part of that.
The query mentions "private event" and "group booking," which falls under the reservations document. The reservations doc handles group bookings, policies, and how to make reservations. The upcoming events doc is for public events, not private ones. Also, customized packages would involve the venue's facilities and policies, which are covered in the venue information and reservations docs.
The crossover topics list clearly states that group bookings are handled by the reservations document. So, the upcoming events document doesn't have info on private events or group bookings. Therefore, the decision should be to exclude the events document here.
</think>
{
"reasoning": "The query asks about arranging a private event or group booking with a customized package, which falls under group booking policies and reservation details. The upcoming events document only covers public events like special occasions, weekly/monthly events, or one-off experiences open to all guests. Private events and group booking logistics are explicitly handled by the reservations document, not the upcoming events document. There is no overlap with the contents of the upcoming events document as described in the guidelines.",
"decision": "exclude"
}
<|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 upcoming events document 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 in the upcoming events document:
### UPCOMING EVENTS DOCUMENT CONTENTS ###
There are only 3 types of information and they refer to:
- 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.
-The special one-off events are usually events for special occasions like a business aniversary, New Year's Eve, Christmas, etc.
-One off experiences like a tasting workshop, a live music event, a comedy night, will also be listed here If planned by the venue.
If there are no upcoming events, then the document will be empty.
DO NOT ASSUME ANY OTHER INFORMATION OTHER THAN THE LISTED ABOVE IS IN THE UPCOMING EVENTS DOCUMENT. IF THE QUERY HAS NOTHING TO DO WITH THE ABOVE CONTENTS, THE UPCOMING EVENTS DOCUMENT SHOULD BE EXCLUDED FROM THE CONTEXT.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
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 upcoming events document in your 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 ###
Do you have any special packages for group bookings or private events?
### 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 UPCOMING EVENTS DOCUMENT ###
ALL QUERIES HANDLED SOLELY BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE UPCOMING EVENTS DOCUMENT FROM THE CONTEXT. THESE DOCUMENTS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS 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.
### RESERVATIONS DOCUMENT CONTENTS ###
- 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.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
### MENU DOCUMENT CONTENTS ###
- 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 ###
- 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.
AGAIN ALL THE DOCUMENTS IN THE CROSSOVER TOPICS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS DOCUMENT.
### GUIDELINES ###
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude. This logic also extends to product promotions, happy hours, and special offers.
If The upcoming events document should be included in the context if the query is related to obtaining information about events, special plans, or updates about future activities at the venue.
This logic however will not stretch to queries about booking a table for an event, as this would be handled by the reservations document. The upcoming events document is only for queries about the events themselves.
Also private events and space rentals are not covered in the upcoming events document. These are handled by the reservations document. The upcoming events document only handles events that are open to the public.
If the query is about plans for the next month, the upcoming events document should be included to provide context about the monthly events that the user might be interested in. Even if the core of the query lies elswhere, the upcoming events document will still be useful for the next node in this particular scenario as they can use this information to suggest alternatives to the customer or entice them with the upcming event information.
If the query does not relate to the upcoming events or plans for the coming week, month or ask about one-off events reply "exclude" in the decision field.
<|im_end|>
<|im_start|>assistant
<think>
Okay, let me try to work through this. The user is asking about special packages for group bookings or private events. I need to determine if the upcoming events document is relevant here.
First, looking at the query: "Do you have any special packages for group bookings or private events?" This seems to be about reservations or organizing private events.
The upcoming events document, as per the guidelines, includes info on one-off, weekly, or monthly events that are open to the public. Private events and group bookings are handled by the reservations document, not the upcoming events.
The crossover topics mention that reservations document covers group bookings and private events. Since the query is about group bookings or private event packages, the relevant info would be in reservations, not upcoming events. Therefore, including the events document here isn't necessary.
The guidelines state that private events and space rentals are handled by reservations, so upcoming events should be excluded. Hence, the decision is to exclude the upcoming events document.
</think>
{
"reasoning": "The query asks about special packages for group bookings or private events, which are related to reservation policies and group handling. The reservations document specifically covers information on how groups and large bookings are handled, including details on private events and reservation policies. The upcoming events document does not contain information on private event packages or group bookings, as these are managed through the reservations process. Therefore, the upcoming events document is not relevant to answering this query.",
"decision": "exclude"
}
<|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 upcoming events document 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 in the upcoming events document:
### UPCOMING EVENTS DOCUMENT CONTENTS ###
There are only 3 types of information and they refer to:
- 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.
-The special one-off events are usually events for special occasions like a business aniversary, New Year's Eve, Christmas, etc.
-One off experiences like a tasting workshop, a live music event, a comedy night, will also be listed here If planned by the venue.
If there are no upcoming events, then the document will be empty.
DO NOT ASSUME ANY OTHER INFORMATION OTHER THAN THE LISTED ABOVE IS IN THE UPCOMING EVENTS DOCUMENT. IF THE QUERY HAS NOTHING TO DO WITH THE ABOVE CONTENTS, THE UPCOMING EVENTS DOCUMENT SHOULD BE EXCLUDED FROM THE CONTEXT.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
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 upcoming events document in your 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 ###
Are group bookings or private events available with tailored packages?
### 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 UPCOMING EVENTS DOCUMENT ###
ALL QUERIES HANDLED SOLELY BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE UPCOMING EVENTS DOCUMENT FROM THE CONTEXT. THESE DOCUMENTS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS 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.
### RESERVATIONS DOCUMENT CONTENTS ###
- 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.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
### MENU DOCUMENT CONTENTS ###
- 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 ###
- 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.
AGAIN ALL THE DOCUMENTS IN THE CROSSOVER TOPICS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS DOCUMENT.
### GUIDELINES ###
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude. This logic also extends to product promotions, happy hours, and special offers.
If The upcoming events document should be included in the context if the query is related to obtaining information about events, special plans, or updates about future activities at the venue.
This logic however will not stretch to queries about booking a table for an event, as this would be handled by the reservations document. The upcoming events document is only for queries about the events themselves.
Also private events and space rentals are not covered in the upcoming events document. These are handled by the reservations document. The upcoming events document only handles events that are open to the public.
If the query is about plans for the next month, the upcoming events document should be included to provide context about the monthly events that the user might be interested in. Even if the core of the query lies elswhere, the upcoming events document will still be useful for the next node in this particular scenario as they can use this information to suggest alternatives to the customer or entice them with the upcming event information.
If the query does not relate to the upcoming events or plans for the coming week, month or ask about one-off events reply "exclude" in the decision field.
<|im_end|>
<|im_start|>assistant
<think>
Okay, let's analyze this query. The user is asking about group bookings or private events with tailored packages. First, I need to check what each document covers.
The upcoming events document includes info on special one-off events, weekly/monthly events, and their details like dates and tickets. But group bookings and private events are more about reservations and venue policies.
Looking at the crossover topics, the reservations document handles group bookings, private events, and related policies. The venue information document might have capacity and facilities details. The query here is about availability and packages, which falls under reservations, not the events open to the public mentioned in the upcoming events document.
Since the user isn't asking about attending a specific event but rather organizing their own private event or group booking, the upcoming events document isn't relevant here. The answer should be exclude because reservations and venue info documents cover this query.
</think>
{
"reasoning": "The query asks about group bookings and private events with tailored packages. These topics are specifically addressed in the reservations document, which handles policies and procedures for reservations, group bookings, and private events. The upcoming events document only covers public events like special occasions or weekly/monthly activities, not private bookings or group reservation policies. Since the user's request pertains to organizing private events or group reservations (not attending public events), the upcoming events document is irrelevant here.",
"decision": "exclude"
}
<|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 upcoming events document 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 in the upcoming events document:
### UPCOMING EVENTS DOCUMENT CONTENTS ###
There are only 3 types of information and they refer to:
- 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.
-The special one-off events are usually events for special occasions like a business aniversary, New Year's Eve, Christmas, etc.
-One off experiences like a tasting workshop, a live music event, a comedy night, will also be listed here If planned by the venue.
If there are no upcoming events, then the document will be empty.
DO NOT ASSUME ANY OTHER INFORMATION OTHER THAN THE LISTED ABOVE IS IN THE UPCOMING EVENTS DOCUMENT. IF THE QUERY HAS NOTHING TO DO WITH THE ABOVE CONTENTS, THE UPCOMING EVENTS DOCUMENT SHOULD BE EXCLUDED FROM THE CONTEXT.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
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 upcoming events document in your 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 ###
Do you offer special packages for private events or group reservations?
### 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 UPCOMING EVENTS DOCUMENT ###
ALL QUERIES HANDLED SOLELY BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE UPCOMING EVENTS DOCUMENT FROM THE CONTEXT. THESE DOCUMENTS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS 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.
### RESERVATIONS DOCUMENT CONTENTS ###
- 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.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
### MENU DOCUMENT CONTENTS ###
- 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 ###
- 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.
AGAIN ALL THE DOCUMENTS IN THE CROSSOVER TOPICS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS DOCUMENT.
### GUIDELINES ###
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude. This logic also extends to product promotions, happy hours, and special offers.
If The upcoming events document should be included in the context if the query is related to obtaining information about events, special plans, or updates about future activities at the venue.
This logic however will not stretch to queries about booking a table for an event, as this would be handled by the reservations document. The upcoming events document is only for queries about the events themselves.
Also private events and space rentals are not covered in the upcoming events document. These are handled by the reservations document. The upcoming events document only handles events that are open to the public.
If the query is about plans for the next month, the upcoming events document should be included to provide context about the monthly events that the user might be interested in. Even if the core of the query lies elswhere, the upcoming events document will still be useful for the next node in this particular scenario as they can use this information to suggest alternatives to the customer or entice them with the upcming event information.
If the query does not relate to the upcoming events or plans for the coming week, month or ask about one-off events reply "exclude" in the decision field.
<|im_end|>
<|im_start|>assistant
<think>
Okay, let's tackle this query: "Do you offer special packages for private events or group reservations?"
First, I need to check if this falls under the upcoming events document. The upcoming events document covers one-off events, weekly or monthly happenings that are open to the public, like live music or workshops. Private events and group reservations aren't listed there. Instead, the reservations document handles group bookings, policies, and packages for private events. Since the user is asking about special packages and reservations, the relevant info would be in the reservations document, not upcoming events. Therefore, excluding the events document makes sense because the query is about services handled by another document.
</think>
{
"reasoning": "The query asks about special packages for private events or group reservations, which pertains to reservation policies and group handling. The upcoming events document does not cover private events or group reservation packages; these are addressed in the reservations document. Since the query relates to services managed by the reservations document, the upcoming events document is not relevant here.",
"decision": "exclude"
}
<|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 upcoming events document 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 in the upcoming events document:
### UPCOMING EVENTS DOCUMENT CONTENTS ###
There are only 3 types of information and they refer to:
- 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.
-The special one-off events are usually events for special occasions like a business aniversary, New Year's Eve, Christmas, etc.
-One off experiences like a tasting workshop, a live music event, a comedy night, will also be listed here If planned by the venue.
If there are no upcoming events, then the document will be empty.
DO NOT ASSUME ANY OTHER INFORMATION OTHER THAN THE LISTED ABOVE IS IN THE UPCOMING EVENTS DOCUMENT. IF THE QUERY HAS NOTHING TO DO WITH THE ABOVE CONTENTS, THE UPCOMING EVENTS DOCUMENT SHOULD BE EXCLUDED FROM THE CONTEXT.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
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 upcoming events document in your 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 ###
Can I book a private event or group gathering with a special package deal?
### 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 UPCOMING EVENTS DOCUMENT ###
ALL QUERIES HANDLED SOLELY BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE UPCOMING EVENTS DOCUMENT FROM THE CONTEXT. THESE DOCUMENTS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS 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.
### RESERVATIONS DOCUMENT CONTENTS ###
- 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.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
### MENU DOCUMENT CONTENTS ###
- 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 ###
- 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.
AGAIN ALL THE DOCUMENTS IN THE CROSSOVER TOPICS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS DOCUMENT.
### GUIDELINES ###
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude. This logic also extends to product promotions, happy hours, and special offers.
If The upcoming events document should be included in the context if the query is related to obtaining information about events, special plans, or updates about future activities at the venue.
This logic however will not stretch to queries about booking a table for an event, as this would be handled by the reservations document. The upcoming events document is only for queries about the events themselves.
Also private events and space rentals are not covered in the upcoming events document. These are handled by the reservations document. The upcoming events document only handles events that are open to the public.
If the query is about plans for the next month, the upcoming events document should be included to provide context about the monthly events that the user might be interested in. Even if the core of the query lies elswhere, the upcoming events document will still be useful for the next node in this particular scenario as they can use this information to suggest alternatives to the customer or entice them with the upcming event information.
If the query does not relate to the upcoming events or plans for the coming week, month or ask about one-off events reply "exclude" in the decision field.
<|im_end|>
<|im_start|>assistant
<think>
Okay, let's break this down. The user is asking about booking a private event or group gathering with a special package deal. I need to determine if the upcoming events document is relevant here.
First, looking at the contents of the upcoming events document: it's about one-off or recurring events open to the public, like workshops, live music, or holiday celebrations. Private events and group bookings aren't listed there. Instead, the reservations document handles group bookings, private events, and package deals.
The query specifically mentions "private event" and "special package deal," which points towards the reservations document where policies on group reservations, minimum spends, and special arrangements are covered. The upcoming events document doesn't deal with private bookings or package deals—it's more about public events and their details.
Also, the guidelines state that private events and space rentals are handled by the reservations document. Since the user isn't asking about attending a public event but rather organizing their own private one, the upcoming events document isn't needed here. So, the decision should be to exclude it.
</think>
{
"reasoning": "The query is about booking a private event or group gathering with a special package deal. This type of request falls under group bookings and private events, which are explicitly handled by the reservations document. The upcoming events document only contains information about public events (e.g., live music, workshops, holidays) and does not cover private bookings, group reservations, or package deals. Therefore, the upcoming events document is not relevant to answering this query.",
"decision": "exclude"
}
<|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 upcoming events document 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 in the upcoming events document:
### UPCOMING EVENTS DOCUMENT CONTENTS ###
There are only 3 types of information and they refer to:
- 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.
-The special one-off events are usually events for special occasions like a business aniversary, New Year's Eve, Christmas, etc.
-One off experiences like a tasting workshop, a live music event, a comedy night, will also be listed here If planned by the venue.
If there are no upcoming events, then the document will be empty.
DO NOT ASSUME ANY OTHER INFORMATION OTHER THAN THE LISTED ABOVE IS IN THE UPCOMING EVENTS DOCUMENT. IF THE QUERY HAS NOTHING TO DO WITH THE ABOVE CONTENTS, THE UPCOMING EVENTS DOCUMENT SHOULD BE EXCLUDED FROM THE CONTEXT.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
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 upcoming events document in your 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 ###
Do you offer exclusive packages for group bookings or private events?
### 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 UPCOMING EVENTS DOCUMENT ###
ALL QUERIES HANDLED SOLELY BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE UPCOMING EVENTS DOCUMENT FROM THE CONTEXT. THESE DOCUMENTS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS 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.
### RESERVATIONS DOCUMENT CONTENTS ###
- 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.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
### MENU DOCUMENT CONTENTS ###
- 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 ###
- 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.
AGAIN ALL THE DOCUMENTS IN THE CROSSOVER TOPICS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS DOCUMENT.
### GUIDELINES ###
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude. This logic also extends to product promotions, happy hours, and special offers.
If The upcoming events document should be included in the context if the query is related to obtaining information about events, special plans, or updates about future activities at the venue.
This logic however will not stretch to queries about booking a table for an event, as this would be handled by the reservations document. The upcoming events document is only for queries about the events themselves.
Also private events and space rentals are not covered in the upcoming events document. These are handled by the reservations document. The upcoming events document only handles events that are open to the public.
If the query is about plans for the next month, the upcoming events document should be included to provide context about the monthly events that the user might be interested in. Even if the core of the query lies elswhere, the upcoming events document will still be useful for the next node in this particular scenario as they can use this information to suggest alternatives to the customer or entice them with the upcming event information.
If the query does not relate to the upcoming events or plans for the coming week, month or ask about one-off events reply "exclude" in the decision field.
<|im_end|>
<|im_start|>assistant
<think>
Okay, let's break down this query. The user is asking about exclusive packages for group bookings or private events. First, I need to determine which document would handle this. The upcoming events document includes public events like special one-offs, weekly, or monthly happenings. However, group bookings and private events are more about reservations and venue policies. Checking the crossover topics, the reservations document covers group handling, reservation policies, and private events. The venue info might have capacity details, but the main handling is in reservations. Since the query is about packages and bookings, not public events, the upcoming events document isn't relevant here. So, exclude it.
</think>
{
"reasoning": "The query asks about exclusive packages for group bookings or private events. These topics are related to reservation policies, group handling, and venue capacity, which fall under the scope of the reservations document. The upcoming events document specifically covers public events such as one-off specials, weekly/monthly activities, and ticketed experiences. Since private events and group booking packages are managed through reservations and venue policies, the upcoming events document does not contain relevant information to address this query.",
"decision": "exclude"
}
<|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 upcoming events document 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 in the upcoming events document:
### UPCOMING EVENTS DOCUMENT CONTENTS ###
There are only 3 types of information and they refer to:
- 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.
-The special one-off events are usually events for special occasions like a business aniversary, New Year's Eve, Christmas, etc.
-One off experiences like a tasting workshop, a live music event, a comedy night, will also be listed here If planned by the venue.
If there are no upcoming events, then the document will be empty.
DO NOT ASSUME ANY OTHER INFORMATION OTHER THAN THE LISTED ABOVE IS IN THE UPCOMING EVENTS DOCUMENT. IF THE QUERY HAS NOTHING TO DO WITH THE ABOVE CONTENTS, THE UPCOMING EVENTS DOCUMENT SHOULD BE EXCLUDED FROM THE CONTEXT.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
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 upcoming events document in your 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 ###
Are there customizable packages for group bookings or private events?
### 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 UPCOMING EVENTS DOCUMENT ###
ALL QUERIES HANDLED SOLELY BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE UPCOMING EVENTS DOCUMENT FROM THE CONTEXT. THESE DOCUMENTS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS 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.
### RESERVATIONS DOCUMENT CONTENTS ###
- 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.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
### MENU DOCUMENT CONTENTS ###
- 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 ###
- 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.
AGAIN ALL THE DOCUMENTS IN THE CROSSOVER TOPICS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS DOCUMENT.
### GUIDELINES ###
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude. This logic also extends to product promotions, happy hours, and special offers.
If The upcoming events document should be included in the context if the query is related to obtaining information about events, special plans, or updates about future activities at the venue.
This logic however will not stretch to queries about booking a table for an event, as this would be handled by the reservations document. The upcoming events document is only for queries about the events themselves.
Also private events and space rentals are not covered in the upcoming events document. These are handled by the reservations document. The upcoming events document only handles events that are open to the public.
If the query is about plans for the next month, the upcoming events document should be included to provide context about the monthly events that the user might be interested in. Even if the core of the query lies elswhere, the upcoming events document will still be useful for the next node in this particular scenario as they can use this information to suggest alternatives to the customer or entice them with the upcming event information.
If the query does not relate to the upcoming events or plans for the coming week, month or ask about one-off events reply "exclude" in the decision field.
<|im_end|>
<|im_start|>assistant
<think>
Okay, let's start by looking at the user's query: "Are there customizable packages for group bookings or private events?" The user is asking about packages for group bookings or private events, which involves customization options.
First, I need to determine which document handles this type of information. The upcoming events document, as per the guidelines, covers special one-off events, weekly or monthly events open to the public. It doesn't include information about private events or group booking packages. Those topics are handled by the reservations document, which includes details on how groups and large bookings are managed, policies, and reservation procedures.
The query specifically mentions "customizable packages," which likely relates to reservation policies, pricing, or special arrangements for private events. Since the reservations document covers group bookings and private events, the upcoming events document isn't needed here. There's no mention of public events, special occasions, or dates tied to events in the query. Therefore, the upcoming events document isn't relevant and should be excluded.
</think>
{
"reasoning": "The query asks about customizable packages for group bookings or private events, which falls under the reservations document's responsibility (handling group bookings, reservation policies, and private events). The upcoming events document only contains information about public events like special occasions, weekly/monthly events, and does not cover private event packages or group booking policies. Therefore, the upcoming events document is irrelevant to this query.",
"decision": "exclude"
}
<|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 upcoming events document 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 in the upcoming events document:
### UPCOMING EVENTS DOCUMENT CONTENTS ###
There are only 3 types of information and they refer to:
- 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.
-The special one-off events are usually events for special occasions like a business aniversary, New Year's Eve, Christmas, etc.
-One off experiences like a tasting workshop, a live music event, a comedy night, will also be listed here If planned by the venue.
If there are no upcoming events, then the document will be empty.
DO NOT ASSUME ANY OTHER INFORMATION OTHER THAN THE LISTED ABOVE IS IN THE UPCOMING EVENTS DOCUMENT. IF THE QUERY HAS NOTHING TO DO WITH THE ABOVE CONTENTS, THE UPCOMING EVENTS DOCUMENT SHOULD BE EXCLUDED FROM THE CONTEXT.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
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 upcoming events document in your 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 ###
Can I reserve a private event or group booking with a unique package?
### 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 UPCOMING EVENTS DOCUMENT ###
ALL QUERIES HANDLED SOLELY BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE UPCOMING EVENTS DOCUMENT FROM THE CONTEXT. THESE DOCUMENTS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS 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.
### RESERVATIONS DOCUMENT CONTENTS ###
- 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.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
### MENU DOCUMENT CONTENTS ###
- 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 ###
- 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.
AGAIN ALL THE DOCUMENTS IN THE CROSSOVER TOPICS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS DOCUMENT.
### GUIDELINES ###
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude. This logic also extends to product promotions, happy hours, and special offers.
If The upcoming events document should be included in the context if the query is related to obtaining information about events, special plans, or updates about future activities at the venue.
This logic however will not stretch to queries about booking a table for an event, as this would be handled by the reservations document. The upcoming events document is only for queries about the events themselves.
Also private events and space rentals are not covered in the upcoming events document. These are handled by the reservations document. The upcoming events document only handles events that are open to the public.
If the query is about plans for the next month, the upcoming events document should be included to provide context about the monthly events that the user might be interested in. Even if the core of the query lies elswhere, the upcoming events document will still be useful for the next node in this particular scenario as they can use this information to suggest alternatives to the customer or entice them with the upcming event information.
If the query does not relate to the upcoming events or plans for the coming week, month or ask about one-off events reply "exclude" in the decision field.
<|im_end|>
<|im_start|>assistant
<think>
Okay, let me break this down. The user is asking about reserving a private event or group booking with a unique package. First, I need to check what each document covers. The upcoming events document includes special one-off, weekly, and monthly events that are open to the public, like live music or workshops. Private events and group bookings aren't listed there; those are handled by the reservations document.
The query specifically mentions reservations and private events, which according to the guidelines, falls under the reservations document. The upcoming events document is only for public events. Since the user isn't asking about attending an event but rather organizing their own, the reservations document is the right place. Therefore, including the upcoming events document here isn't necessary. So the decision should be to exclude it.
</think>
{
"reasoning": "The query asks about reserving a private event or group booking, which pertains to reservation policies and structured packages. The upcoming events document only contains information about public events (e.g., live music, workshops) and does not handle private bookings or group reservations. These topics are explicitly covered in the reservations document. Since the query does not relate to public events, event schedules, or event-specific details, the upcoming events document is not relevant here.",
"decision": "exclude"
}
<|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 upcoming events document 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 in the upcoming events document:
### UPCOMING EVENTS DOCUMENT CONTENTS ###
There are only 3 types of information and they refer to:
- 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.
-The special one-off events are usually events for special occasions like a business aniversary, New Year's Eve, Christmas, etc.
-One off experiences like a tasting workshop, a live music event, a comedy night, will also be listed here If planned by the venue.
If there are no upcoming events, then the document will be empty.
DO NOT ASSUME ANY OTHER INFORMATION OTHER THAN THE LISTED ABOVE IS IN THE UPCOMING EVENTS DOCUMENT. IF THE QUERY HAS NOTHING TO DO WITH THE ABOVE CONTENTS, THE UPCOMING EVENTS DOCUMENT SHOULD BE EXCLUDED FROM THE CONTEXT.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
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 upcoming events document in your 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 ###
Do you have any event packages for group bookings or private events?
### 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 UPCOMING EVENTS DOCUMENT ###
ALL QUERIES HANDLED SOLELY BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE UPCOMING EVENTS DOCUMENT FROM THE CONTEXT. THESE DOCUMENTS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS 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.
### RESERVATIONS DOCUMENT CONTENTS ###
- 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.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
### MENU DOCUMENT CONTENTS ###
- 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 ###
- 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.
AGAIN ALL THE DOCUMENTS IN THE CROSSOVER TOPICS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS DOCUMENT.
### GUIDELINES ###
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude. This logic also extends to product promotions, happy hours, and special offers.
If The upcoming events document should be included in the context if the query is related to obtaining information about events, special plans, or updates about future activities at the venue.
This logic however will not stretch to queries about booking a table for an event, as this would be handled by the reservations document. The upcoming events document is only for queries about the events themselves.
Also private events and space rentals are not covered in the upcoming events document. These are handled by the reservations document. The upcoming events document only handles events that are open to the public.
If the query is about plans for the next month, the upcoming events document should be included to provide context about the monthly events that the user might be interested in. Even if the core of the query lies elswhere, the upcoming events document will still be useful for the next node in this particular scenario as they can use this information to suggest alternatives to the customer or entice them with the upcming event information.
If the query does not relate to the upcoming events or plans for the coming week, month or ask about one-off events reply "exclude" in the decision field.
<|im_end|>
<|im_start|>assistant
<think>
Okay, let's see. The user is asking about event packages for group bookings or private events. I need to determine if the upcoming events document is relevant here.
First, the upcoming events document includes special one-off events, weekly events, and monthly events, like live music, comedy nights, or holiday celebrations. These are typically open to the public, not private bookings.
The user's query is about group bookings or private events. From the guidelines, private events and space rentals are handled by the reservations document, not the events document. The reservations document has info on how groups and large bookings are managed, including policies and reservation processes.
The events document doesn't cover private event packages; it's more about public events. So, since the query is related to group bookings or private events, it's under the reservations document's scope. Therefore, the upcoming events document should be excluded.
</think>
{
"reasoning": "The query asks about event packages for group bookings or private events. The upcoming events document specifically covers public events such as one-off special occasions, weekly/monthly activities, and ticketed experiences. Private events, group booking policies, and venue rental details are explicitly handled by the reservations document, which includes information on minimum spends, group handling, and reservation procedures. Since the query relates to private or group-specific arrangements rather than public events, the upcoming events document does not contain relevant information for this request.",
"decision": "exclude"
}
<|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 upcoming events document 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 in the upcoming events document:
### UPCOMING EVENTS DOCUMENT CONTENTS ###
There are only 3 types of information and they refer to:
- 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.
-The special one-off events are usually events for special occasions like a business aniversary, New Year's Eve, Christmas, etc.
-One off experiences like a tasting workshop, a live music event, a comedy night, will also be listed here If planned by the venue.
If there are no upcoming events, then the document will be empty.
DO NOT ASSUME ANY OTHER INFORMATION OTHER THAN THE LISTED ABOVE IS IN THE UPCOMING EVENTS DOCUMENT. IF THE QUERY HAS NOTHING TO DO WITH THE ABOVE CONTENTS, THE UPCOMING EVENTS DOCUMENT SHOULD BE EXCLUDED FROM THE CONTEXT.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
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 upcoming events document in your 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 ###
Are there specific packages for private events or group bookings?
### 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 UPCOMING EVENTS DOCUMENT ###
ALL QUERIES HANDLED SOLELY BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE UPCOMING EVENTS DOCUMENT FROM THE CONTEXT. THESE DOCUMENTS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS 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.
### RESERVATIONS DOCUMENT CONTENTS ###
- 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.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
### MENU DOCUMENT CONTENTS ###
- 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 ###
- 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.
AGAIN ALL THE DOCUMENTS IN THE CROSSOVER TOPICS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS DOCUMENT.
### GUIDELINES ###
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude. This logic also extends to product promotions, happy hours, and special offers.
If The upcoming events document should be included in the context if the query is related to obtaining information about events, special plans, or updates about future activities at the venue.
This logic however will not stretch to queries about booking a table for an event, as this would be handled by the reservations document. The upcoming events document is only for queries about the events themselves.
Also private events and space rentals are not covered in the upcoming events document. These are handled by the reservations document. The upcoming events document only handles events that are open to the public.
If the query is about plans for the next month, the upcoming events document should be included to provide context about the monthly events that the user might be interested in. Even if the core of the query lies elswhere, the upcoming events document will still be useful for the next node in this particular scenario as they can use this information to suggest alternatives to the customer or entice them with the upcming event information.
If the query does not relate to the upcoming events or plans for the coming week, month or ask about one-off events reply "exclude" in the decision field.
<|im_end|>
<|im_start|>assistant
<think>
Okay, let me process this query step by step. The user is asking about specific packages for private events or group bookings. I need to determine if the upcoming events document is relevant here.
First, I recall the contents of the upcoming events document. It includes special one-off events, weekly or monthly events, like live music or workshops. Private events and group bookings aren't part of that; those are handled by the reservations document. The guidelines mention that private events and space rentals are covered in reservations, not upcoming events.
The query is specifically about packages for private events or group bookings. Since the reservations document handles group bookings and private event policies, the upcoming events document doesn't contain info on packages or booking policies. Therefore, including it wouldn't help answer the user's question. The correct document here is reservations, so the upcoming events document should be excluded.
</think>
{
"reasoning": "The query asks about specific packages for private events or group bookings. The upcoming events document does not include information on private events, group booking policies, or venue packages, as these are explicitly covered in the reservations document. Since the query pertains to group booking logistics rather than public events listed in the upcoming events document, excluding it ensures the next node focuses on the correct context (reservations document) for an accurate response.",
"decision": "exclude"
}
<|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 upcoming events document 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 in the upcoming events document:
### UPCOMING EVENTS DOCUMENT CONTENTS ###
There are only 3 types of information and they refer to:
- 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.
-The special one-off events are usually events for special occasions like a business aniversary, New Year's Eve, Christmas, etc.
-One off experiences like a tasting workshop, a live music event, a comedy night, will also be listed here If planned by the venue.
If there are no upcoming events, then the document will be empty.
DO NOT ASSUME ANY OTHER INFORMATION OTHER THAN THE LISTED ABOVE IS IN THE UPCOMING EVENTS DOCUMENT. IF THE QUERY HAS NOTHING TO DO WITH THE ABOVE CONTENTS, THE UPCOMING EVENTS DOCUMENT SHOULD BE EXCLUDED FROM THE CONTEXT.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
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 upcoming events document in your 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 ###
Can I get a package deal for group bookings or private events?
### 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 UPCOMING EVENTS DOCUMENT ###
ALL QUERIES HANDLED SOLELY BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE UPCOMING EVENTS DOCUMENT FROM THE CONTEXT. THESE DOCUMENTS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS 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.
### RESERVATIONS DOCUMENT CONTENTS ###
- 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.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
### MENU DOCUMENT CONTENTS ###
- 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 ###
- 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.
AGAIN ALL THE DOCUMENTS IN THE CROSSOVER TOPICS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS DOCUMENT.
### GUIDELINES ###
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude. This logic also extends to product promotions, happy hours, and special offers.
If The upcoming events document should be included in the context if the query is related to obtaining information about events, special plans, or updates about future activities at the venue.
This logic however will not stretch to queries about booking a table for an event, as this would be handled by the reservations document. The upcoming events document is only for queries about the events themselves.
Also private events and space rentals are not covered in the upcoming events document. These are handled by the reservations document. The upcoming events document only handles events that are open to the public.
If the query is about plans for the next month, the upcoming events document should be included to provide context about the monthly events that the user might be interested in. Even if the core of the query lies elswhere, the upcoming events document will still be useful for the next node in this particular scenario as they can use this information to suggest alternatives to the customer or entice them with the upcming event information.
If the query does not relate to the upcoming events or plans for the coming week, month or ask about one-off events reply "exclude" in the decision field.
<|im_end|>
<|im_start|>assistant
<think>
Okay, let's break this down. The user is asking about package deals for group bookings or private events. First, I need to check what each document covers.
The upcoming events document includes special one-off events like New Year's parties, weekly/monthly events, and their details. But group bookings and private events are mentioned in the reservations document. The query here is specifically about package deals for these types of bookings, which falls under how the venue handles group reservations and private events.
The guidelines say that private events and space rentals are handled by the reservations document, not the events one. Since the user isn't asking about public events or specific upcoming occasions, the events document isn't relevant here. So the decision should be to exclude the upcoming events document because the answer lies in the reservations document instead.
</think>
{
"reasoning": "The query is about package deals for group bookings or private events, which relates to reservation policies and group handling procedures. The reservations document specifically covers how groups and large bookings are managed, including details about reservations, private events, and package deals. The upcoming events document only contains information about public events (special occasions, weekly/monthly programming), not private bookings or group reservation packages. Since the query falls under the reservations document's scope, the upcoming events document is irrelevant here.",
"decision": "exclude"
}
<|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 upcoming events document 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 in the upcoming events document:
### UPCOMING EVENTS DOCUMENT CONTENTS ###
There are only 3 types of information and they refer to:
- 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.
-The special one-off events are usually events for special occasions like a business aniversary, New Year's Eve, Christmas, etc.
-One off experiences like a tasting workshop, a live music event, a comedy night, will also be listed here If planned by the venue.
If there are no upcoming events, then the document will be empty.
DO NOT ASSUME ANY OTHER INFORMATION OTHER THAN THE LISTED ABOVE IS IN THE UPCOMING EVENTS DOCUMENT. IF THE QUERY HAS NOTHING TO DO WITH THE ABOVE CONTENTS, THE UPCOMING EVENTS DOCUMENT SHOULD BE EXCLUDED FROM THE CONTEXT.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
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 upcoming events document in your 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 ###
Do you provide special event packages for private gatherings or group bookings?
### 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 UPCOMING EVENTS DOCUMENT ###
ALL QUERIES HANDLED SOLELY BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE UPCOMING EVENTS DOCUMENT FROM THE CONTEXT. THESE DOCUMENTS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS 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.
### RESERVATIONS DOCUMENT CONTENTS ###
- 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.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
### MENU DOCUMENT CONTENTS ###
- 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 ###
- 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.
AGAIN ALL THE DOCUMENTS IN THE CROSSOVER TOPICS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS DOCUMENT.
### GUIDELINES ###
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude. This logic also extends to product promotions, happy hours, and special offers.
If The upcoming events document should be included in the context if the query is related to obtaining information about events, special plans, or updates about future activities at the venue.
This logic however will not stretch to queries about booking a table for an event, as this would be handled by the reservations document. The upcoming events document is only for queries about the events themselves.
Also private events and space rentals are not covered in the upcoming events document. These are handled by the reservations document. The upcoming events document only handles events that are open to the public.
If the query is about plans for the next month, the upcoming events document should be included to provide context about the monthly events that the user might be interested in. Even if the core of the query lies elswhere, the upcoming events document will still be useful for the next node in this particular scenario as they can use this information to suggest alternatives to the customer or entice them with the upcming event information.
If the query does not relate to the upcoming events or plans for the coming week, month or ask about one-off events reply "exclude" in the decision field.
<|im_end|>
<|im_start|>assistant
<think>
Okay, let's break down the user's query. They're asking if the venue provides special event packages for private gatherings or group bookings. First, I need to figure out where this information would be located based on the documents outlined.
The Upcoming Events Document includes details about public events like live music, comedy nights, workshops, and special occasions. However, private events or group bookings aren't covered here. Those fall under the Reservations Document, which handles policies on group bookings, minimum spends, and how to make reservations for private events.
The query specifically mentions "private gatherings" and "group bookings," which align with the Reservations Document's content about handling large groups and reservation policies. Since the Upcoming Events Document doesn't deal with private or group bookings but rather public events, it's not relevant here. Therefore, the correct decision is to exclude the Upcoming Events Document from the context because the answer is found elsewhere.
</think>
{
"reasoning": "The query is about special event packages for private gatherings or group bookings. The upcoming events document does not handle private events or space rentals; such queries are managed by the reservations document, which covers group booking policies, minimum spends, and reservation procedures. Since the question pertains to private or group-specific arrangements rather than public events listed in the upcoming events document, excluding it is appropriate.",
"decision": "exclude"
}
<|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 upcoming events document 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 in the upcoming events document:
### UPCOMING EVENTS DOCUMENT CONTENTS ###
There are only 3 types of information and they refer to:
- 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.
-The special one-off events are usually events for special occasions like a business aniversary, New Year's Eve, Christmas, etc.
-One off experiences like a tasting workshop, a live music event, a comedy night, will also be listed here If planned by the venue.
If there are no upcoming events, then the document will be empty.
DO NOT ASSUME ANY OTHER INFORMATION OTHER THAN THE LISTED ABOVE IS IN THE UPCOMING EVENTS DOCUMENT. IF THE QUERY HAS NOTHING TO DO WITH THE ABOVE CONTENTS, THE UPCOMING EVENTS DOCUMENT SHOULD BE EXCLUDED FROM THE CONTEXT.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
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 upcoming events document in your 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 ###
Do you offer private event or group booking packages for large groups?
### 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 UPCOMING EVENTS DOCUMENT ###
ALL QUERIES HANDLED SOLELY BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE UPCOMING EVENTS DOCUMENT FROM THE CONTEXT. THESE DOCUMENTS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS 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.
### RESERVATIONS DOCUMENT CONTENTS ###
- 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.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
### MENU DOCUMENT CONTENTS ###
- 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 ###
- 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.
AGAIN ALL THE DOCUMENTS IN THE CROSSOVER TOPICS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS DOCUMENT.
### GUIDELINES ###
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude. This logic also extends to product promotions, happy hours, and special offers.
If The upcoming events document should be included in the context if the query is related to obtaining information about events, special plans, or updates about future activities at the venue.
This logic however will not stretch to queries about booking a table for an event, as this would be handled by the reservations document. The upcoming events document is only for queries about the events themselves.
Also private events and space rentals are not covered in the upcoming events document. These are handled by the reservations document. The upcoming events document only handles events that are open to the public.
If the query is about plans for the next month, the upcoming events document should be included to provide context about the monthly events that the user might be interested in. Even if the core of the query lies elswhere, the upcoming events document will still be useful for the next node in this particular scenario as they can use this information to suggest alternatives to the customer or entice them with the upcming event information.
If the query does not relate to the upcoming events or plans for the coming week, month or ask about one-off events reply "exclude" in the decision field.
<|im_end|>
<|im_start|>assistant
<think>
Okay, let's tackle this query: "Do you offer private event or group booking packages for large groups?"
First, I need to check what the user is asking about. They're inquiring about private events or group booking packages. Now, looking at the upcoming events document contents, it covers special one-off events, weekly/monthly events, and details like date, time, tickets, and descriptions. Private events and group bookings aren't listed there.
Next, the crossover topics mention that reservations document handles group bookings, reservations policies, and how large groups are managed. The guidelines also state that private events and space rentals are handled by the reservations document, not the upcoming events. Since the user's question is about booking packages for groups, the answer would be found in the reservations document, not the upcoming events. Therefore, the upcoming events document isn't relevant here and should be excluded.
</think>
{
"reasoning": "The query asks about private event or group booking packages, which pertain to reservation policies and handling of large groups. According to the guidelines, private events and group bookings are handled by the reservations document, not the upcoming events document. The upcoming events document does not contain information about private bookings or group reservation packages, as it focuses on public events like special occasions or recurring weekly/monthly activities. Therefore, the upcoming events document is not relevant to this query.",
"decision": "exclude"
}
<|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 upcoming events document 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 in the upcoming events document:
### UPCOMING EVENTS DOCUMENT CONTENTS ###
There are only 3 types of information and they refer to:
- 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.
-The special one-off events are usually events for special occasions like a business aniversary, New Year's Eve, Christmas, etc.
-One off experiences like a tasting workshop, a live music event, a comedy night, will also be listed here If planned by the venue.
If there are no upcoming events, then the document will be empty.
DO NOT ASSUME ANY OTHER INFORMATION OTHER THAN THE LISTED ABOVE IS IN THE UPCOMING EVENTS DOCUMENT. IF THE QUERY HAS NOTHING TO DO WITH THE ABOVE CONTENTS, THE UPCOMING EVENTS DOCUMENT SHOULD BE EXCLUDED FROM THE CONTEXT.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
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 upcoming events document in your 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 ###
Are there event packages available for private or group bookings?
### 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 UPCOMING EVENTS DOCUMENT ###
ALL QUERIES HANDLED SOLELY BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE UPCOMING EVENTS DOCUMENT FROM THE CONTEXT. THESE DOCUMENTS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS 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.
### RESERVATIONS DOCUMENT CONTENTS ###
- 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.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
### MENU DOCUMENT CONTENTS ###
- 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 ###
- 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.
AGAIN ALL THE DOCUMENTS IN THE CROSSOVER TOPICS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS DOCUMENT.
### GUIDELINES ###
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude. This logic also extends to product promotions, happy hours, and special offers.
If The upcoming events document should be included in the context if the query is related to obtaining information about events, special plans, or updates about future activities at the venue.
This logic however will not stretch to queries about booking a table for an event, as this would be handled by the reservations document. The upcoming events document is only for queries about the events themselves.
Also private events and space rentals are not covered in the upcoming events document. These are handled by the reservations document. The upcoming events document only handles events that are open to the public.
If the query is about plans for the next month, the upcoming events document should be included to provide context about the monthly events that the user might be interested in. Even if the core of the query lies elswhere, the upcoming events document will still be useful for the next node in this particular scenario as they can use this information to suggest alternatives to the customer or entice them with the upcming event information.
If the query does not relate to the upcoming events or plans for the coming week, month or ask about one-off events reply "exclude" in the decision field.
<|im_end|>
<|im_start|>assistant
<think>
Okay, let's break down this query. The user is asking about event packages for private or group bookings.
First, I check what's in the upcoming events document. That document covers special one-off events, weekly/monthly recurring events, and their details like dates, tickets, descriptions. But private or group bookings? Hmm, the reservations document handles group bookings, reservations policies, minimum spends, cancellations. The problem says if the query is about group bookings handled by reservations, then events document should be excluded.
The user's question is about event packages specifically for private or group bookings. Even though "event" is mentioned, the context here is about booking for groups, which is under reservations. The upcoming events document doesn't handle private events or space rentals; those are in reservations. So even if there's an event package, if it's about booking for a group, that's not in events. Therefore, the decision should be to exclude the upcoming events document.
</think>
{
"reasoning": "The query asks about event packages for private or group bookings, which pertains to how group reservations and private events are managed. The reservations document explicitly handles group bookings, policies, and reservation logistics, while the upcoming events document only covers publicly accessible events like weekly specials or one-off experiences. Since private/group booking packages fall under reservation policies rather than event details, the upcoming events document is not relevant here.",
"decision": "exclude"
}
<|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 upcoming events document 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 in the upcoming events document:
### UPCOMING EVENTS DOCUMENT CONTENTS ###
There are only 3 types of information and they refer to:
- 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.
-The special one-off events are usually events for special occasions like a business aniversary, New Year's Eve, Christmas, etc.
-One off experiences like a tasting workshop, a live music event, a comedy night, will also be listed here If planned by the venue.
If there are no upcoming events, then the document will be empty.
DO NOT ASSUME ANY OTHER INFORMATION OTHER THAN THE LISTED ABOVE IS IN THE UPCOMING EVENTS DOCUMENT. IF THE QUERY HAS NOTHING TO DO WITH THE ABOVE CONTENTS, THE UPCOMING EVENTS DOCUMENT SHOULD BE EXCLUDED FROM THE CONTEXT.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
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 upcoming events document in your 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 ###
Do you offer any promotions or packages for group or private event bookings?
### 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 UPCOMING EVENTS DOCUMENT ###
ALL QUERIES HANDLED SOLELY BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE UPCOMING EVENTS DOCUMENT FROM THE CONTEXT. THESE DOCUMENTS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS 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.
### RESERVATIONS DOCUMENT CONTENTS ###
- 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.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
### MENU DOCUMENT CONTENTS ###
- 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 ###
- 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.
AGAIN ALL THE DOCUMENTS IN THE CROSSOVER TOPICS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS DOCUMENT.
### GUIDELINES ###
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude. This logic also extends to product promotions, happy hours, and special offers.
If The upcoming events document should be included in the context if the query is related to obtaining information about events, special plans, or updates about future activities at the venue.
This logic however will not stretch to queries about booking a table for an event, as this would be handled by the reservations document. The upcoming events document is only for queries about the events themselves.
Also private events and space rentals are not covered in the upcoming events document. These are handled by the reservations document. The upcoming events document only handles events that are open to the public.
If the query is about plans for the next month, the upcoming events document should be included to provide context about the monthly events that the user might be interested in. Even if the core of the query lies elswhere, the upcoming events document will still be useful for the next node in this particular scenario as they can use this information to suggest alternatives to the customer or entice them with the upcming event information.
If the query does not relate to the upcoming events or plans for the coming week, month or ask about one-off events reply "exclude" in the decision field.
<|im_end|>
<|im_start|>assistant
<think>
Okay, let's tackle this query. The user is asking about promotions or packages for group or private event bookings. I need to determine if the upcoming events document is relevant here.
First, the upcoming events document includes special one-offs, weekly, and monthly events. It's about public events like live music, comedy nights, or holiday celebrations. The query here is about group bookings and private events, which typically involve reservations, pricing, and special packages. Those details are handled by the reservations document, which covers policies, minimum spends, and how groups are managed.
The guidelines mention that private events and space rentals fall under the reservations document, not upcoming events. Since the user's query is specifically about group bookings and private events, the information needed would be in the reservations document. The promotions or packages for such bookings are part of reservation policies, not the public events listed in the upcoming events doc. Therefore, the upcoming events document isn't necessary here. Decision is to exclude.
</think>
{
"reasoning": "The query asks about promotions or packages for group or private event bookings. The upcoming events document does not contain information about group booking policies, private event packages, or promotional offers for reserved spaces. These details are covered in the reservations document, which handles topics like minimum spends, group policies, and private event logistics. Since the query pertains to reservations and service-related promotions rather than public events (e.g., live music, workshops), the upcoming events document is not relevant and should be excluded.",
"decision": "exclude"
}
<|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 upcoming events document 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 in the upcoming events document:
### UPCOMING EVENTS DOCUMENT CONTENTS ###
There are only 3 types of information and they refer to:
- 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.
-The special one-off events are usually events for special occasions like a business aniversary, New Year's Eve, Christmas, etc.
-One off experiences like a tasting workshop, a live music event, a comedy night, will also be listed here If planned by the venue.
If there are no upcoming events, then the document will be empty.
DO NOT ASSUME ANY OTHER INFORMATION OTHER THAN THE LISTED ABOVE IS IN THE UPCOMING EVENTS DOCUMENT. IF THE QUERY HAS NOTHING TO DO WITH THE ABOVE CONTENTS, THE UPCOMING EVENTS DOCUMENT SHOULD BE EXCLUDED FROM THE CONTEXT.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
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 upcoming events document in your 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 ###
Can I book a group event or private gathering with a package deal?
### 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 UPCOMING EVENTS DOCUMENT ###
ALL QUERIES HANDLED SOLELY BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE UPCOMING EVENTS DOCUMENT FROM THE CONTEXT. THESE DOCUMENTS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS 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.
### RESERVATIONS DOCUMENT CONTENTS ###
- 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.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
### MENU DOCUMENT CONTENTS ###
- 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 ###
- 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.
AGAIN ALL THE DOCUMENTS IN THE CROSSOVER TOPICS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS DOCUMENT.
### GUIDELINES ###
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude. This logic also extends to product promotions, happy hours, and special offers.
If The upcoming events document should be included in the context if the query is related to obtaining information about events, special plans, or updates about future activities at the venue.
This logic however will not stretch to queries about booking a table for an event, as this would be handled by the reservations document. The upcoming events document is only for queries about the events themselves.
Also private events and space rentals are not covered in the upcoming events document. These are handled by the reservations document. The upcoming events document only handles events that are open to the public.
If the query is about plans for the next month, the upcoming events document should be included to provide context about the monthly events that the user might be interested in. Even if the core of the query lies elswhere, the upcoming events document will still be useful for the next node in this particular scenario as they can use this information to suggest alternatives to the customer or entice them with the upcming event information.
If the query does not relate to the upcoming events or plans for the coming week, month or ask about one-off events reply "exclude" in the decision field.
<|im_end|>
<|im_start|>assistant
<think>
Okay, let me think through this query step by step. The user is asking about booking a group event or private gathering with a package deal.
First, I need to check what each document covers. The upcoming events document includes information about special one-off events, weekly/monthly events, and their details like dates, tickets, and policies. But the query here isn't about attending an event; it's about organizing a private group booking.
Looking at the crossover topics, the reservations document handles group bookings, private events, and package deals. It includes policies on minimum spends, cancellations, and how to make reservations. The venue information document might have capacity and facilities info, but the main handling is in reservations.
The guidelines mention that private events and space rentals are covered by the reservations document, not upcoming events. Since the user is asking about booking a group event, the answer would rely on the reservations document. Therefore, the upcoming events document isn't needed here. The decision should be to exclude it.
</think>
{
"reasoning": "The query is about booking a group event or private gathering with a package deal. This relates to reservations policies, group handling, and package deals, which are explicitly covered in the reservations document. The upcoming events document does not contain information about private bookings, group policies, or package deals—it only lists public events like workshops, live music, or seasonal celebrations. Therefore, the upcoming events document is irrelevant for this query.",
"decision": "exclude"
}
<|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 upcoming events document 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 in the upcoming events document:
### UPCOMING EVENTS DOCUMENT CONTENTS ###
There are only 3 types of information and they refer to:
- 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.
-The special one-off events are usually events for special occasions like a business aniversary, New Year's Eve, Christmas, etc.
-One off experiences like a tasting workshop, a live music event, a comedy night, will also be listed here If planned by the venue.
If there are no upcoming events, then the document will be empty.
DO NOT ASSUME ANY OTHER INFORMATION OTHER THAN THE LISTED ABOVE IS IN THE UPCOMING EVENTS DOCUMENT. IF THE QUERY HAS NOTHING TO DO WITH THE ABOVE CONTENTS, THE UPCOMING EVENTS DOCUMENT SHOULD BE EXCLUDED FROM THE CONTEXT.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
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 upcoming events document in your 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 ###
Do you provide group booking or private event packages?
### 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 UPCOMING EVENTS DOCUMENT ###
ALL QUERIES HANDLED SOLELY BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE UPCOMING EVENTS DOCUMENT FROM THE CONTEXT. THESE DOCUMENTS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS 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.
### RESERVATIONS DOCUMENT CONTENTS ###
- 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.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
### MENU DOCUMENT CONTENTS ###
- 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 ###
- 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.
AGAIN ALL THE DOCUMENTS IN THE CROSSOVER TOPICS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS DOCUMENT.
### GUIDELINES ###
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude. This logic also extends to product promotions, happy hours, and special offers.
If The upcoming events document should be included in the context if the query is related to obtaining information about events, special plans, or updates about future activities at the venue.
This logic however will not stretch to queries about booking a table for an event, as this would be handled by the reservations document. The upcoming events document is only for queries about the events themselves.
Also private events and space rentals are not covered in the upcoming events document. These are handled by the reservations document. The upcoming events document only handles events that are open to the public.
If the query is about plans for the next month, the upcoming events document should be included to provide context about the monthly events that the user might be interested in. Even if the core of the query lies elswhere, the upcoming events document will still be useful for the next node in this particular scenario as they can use this information to suggest alternatives to the customer or entice them with the upcming event information.
If the query does not relate to the upcoming events or plans for the coming week, month or ask about one-off events reply "exclude" in the decision field.
<|im_end|>
<|im_start|>assistant
<think>
Okay, let's tackle this query. The user is asking, "Do you provide group booking or private event packages?" I need to determine if the upcoming events document is relevant here.
First, I'll recall the contents of the upcoming events document. It includes special one-off events, weekly and monthly events, with details like dates, tickets, and descriptions. Private events or group bookings aren't part of this document.
The guidelines mention that private events and space rentals are handled by the reservations document, not upcoming events. The query specifically asks about group bookings and private event packages, which falls under the reservations document's responsibility.
Cross-checking the crossover topics confirms that group bookings are covered in the reservations document. Since the query is about booking and packages, not public events, the upcoming events document isn't needed here. Therefore, the decision is to exclude it.
</think>
{
"reasoning": "The query asks about group booking or private event packages. According to the guidelines, private events and space rentals are handled by the reservations document, not the upcoming events document. The upcoming events document only contains information about public events like one-off specials, weekly/monthly activities, and does not cover group booking policies or private event packages. Since the query pertains to reservations and bookings, the relevant context is the reservations document, making the upcoming events document unnecessary for answering this query.",
"decision": "exclude"
}
<|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 upcoming events document 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 in the upcoming events document:
### UPCOMING EVENTS DOCUMENT CONTENTS ###
There are only 3 types of information and they refer to:
- 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.
-The special one-off events are usually events for special occasions like a business aniversary, New Year's Eve, Christmas, etc.
-One off experiences like a tasting workshop, a live music event, a comedy night, will also be listed here If planned by the venue.
If there are no upcoming events, then the document will be empty.
DO NOT ASSUME ANY OTHER INFORMATION OTHER THAN THE LISTED ABOVE IS IN THE UPCOMING EVENTS DOCUMENT. IF THE QUERY HAS NOTHING TO DO WITH THE ABOVE CONTENTS, THE UPCOMING EVENTS DOCUMENT SHOULD BE EXCLUDED FROM THE CONTEXT.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
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 upcoming events document in your 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 ###
Can I book a private event or group reservation with a special package?
### 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 UPCOMING EVENTS DOCUMENT ###
ALL QUERIES HANDLED SOLELY BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE UPCOMING EVENTS DOCUMENT FROM THE CONTEXT. THESE DOCUMENTS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS 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.
### RESERVATIONS DOCUMENT CONTENTS ###
- 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.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
### MENU DOCUMENT CONTENTS ###
- 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 ###
- 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.
AGAIN ALL THE DOCUMENTS IN THE CROSSOVER TOPICS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS DOCUMENT.
### GUIDELINES ###
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude. This logic also extends to product promotions, happy hours, and special offers.
If The upcoming events document should be included in the context if the query is related to obtaining information about events, special plans, or updates about future activities at the venue.
This logic however will not stretch to queries about booking a table for an event, as this would be handled by the reservations document. The upcoming events document is only for queries about the events themselves.
Also private events and space rentals are not covered in the upcoming events document. These are handled by the reservations document. The upcoming events document only handles events that are open to the public.
If the query is about plans for the next month, the upcoming events document should be included to provide context about the monthly events that the user might be interested in. Even if the core of the query lies elswhere, the upcoming events document will still be useful for the next node in this particular scenario as they can use this information to suggest alternatives to the customer or entice them with the upcming event information.
If the query does not relate to the upcoming events or plans for the coming week, month or ask about one-off events reply "exclude" in the decision field.
<|im_end|>
<|im_start|>assistant
<think>
Okay, let's break down the user's query: "Can I book a private event or group reservation with a special package?" The user is asking about booking a private event or group reservation, possibly with some special package.
First, I need to check which document handles this type of query. According to the guidelines, private events and group reservations are covered by the reservations document, not the upcoming events document. The upcoming events document includes info on public events like live music, comedy nights, or special occasions. Private bookings, even if they involve special packages, would involve reservations policies, minimum spends, group handling, etc., all of which are in the reservations document.
Looking at the crossover topics, the reservations document specifically handles group bookings, reservation policies, and how to make reservations. The upcoming events document doesn't deal with private bookings but rather lists public events. Since the user is asking about booking their own event, that's a reservation matter. Therefore, the upcoming events document isn't needed here. The answer should come from the reservations document. So, the decision is to exclude the upcoming events document.
</think>
{
"reasoning": "The query is about booking a private event or group reservation with a special package. This falls under group bookings and reservation policies, which are explicitly handled by the reservations document according to the provided guidelines. The upcoming events document does not cover private bookings or reservations, as it focuses on public events like live music, workshops, or special occasions. Therefore, the upcoming events document is not relevant to answering this query.",
"decision": "exclude"
}
<|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 upcoming events document 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 in the upcoming events document:
### UPCOMING EVENTS DOCUMENT CONTENTS ###
There are only 3 types of information and they refer to:
- 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.
-The special one-off events are usually events for special occasions like a business aniversary, New Year's Eve, Christmas, etc.
-One off experiences like a tasting workshop, a live music event, a comedy night, will also be listed here If planned by the venue.
If there are no upcoming events, then the document will be empty.
DO NOT ASSUME ANY OTHER INFORMATION OTHER THAN THE LISTED ABOVE IS IN THE UPCOMING EVENTS DOCUMENT. IF THE QUERY HAS NOTHING TO DO WITH THE ABOVE CONTENTS, THE UPCOMING EVENTS DOCUMENT SHOULD BE EXCLUDED FROM THE CONTEXT.
Make sure to follow the rules set out in the guidelines section of the prompt. To ensure you are making the correct decision.
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 upcoming events document in your 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 ###
Do you offer any packages for group bookings or private events?
### 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 UPCOMING EVENTS DOCUMENT ###
ALL QUERIES HANDLED SOLELY BY THE BELOW DOCUMENTS SHOULD RESULT IN A DECISION TO EXCLUDE THE UPCOMING EVENTS DOCUMENT FROM THE CONTEXT. THESE DOCUMENTS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS 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.
### RESERVATIONS DOCUMENT CONTENTS ###
- 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.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
### MENU DOCUMENT CONTENTS ###
- 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 ###
- 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.
AGAIN ALL THE DOCUMENTS IN THE CROSSOVER TOPICS ARE THEIR OWN INDIVIDUAL CONTEXTS AND SEPERATE FROM THE UPCOMING EVENTS DOCUMENT.
### GUIDELINES ###
All queries that are obviously solely about products are answerable by the menu document alone and should have a decision of exclude. This logic also extends to product promotions, happy hours, and special offers.
If The upcoming events document should be included in the context if the query is related to obtaining information about events, special plans, or updates about future activities at the venue.
This logic however will not stretch to queries about booking a table for an event, as this would be handled by the reservations document. The upcoming events document is only for queries about the events themselves.
Also private events and space rentals are not covered in the upcoming events document. These are handled by the reservations document. The upcoming events document only handles events that are open to the public.
If the query is about plans for the next month, the upcoming events document should be included to provide context about the monthly events that the user might be interested in. Even if the core of the query lies elswhere, the upcoming events document will still be useful for the next node in this particular scenario as they can use this information to suggest alternatives to the customer or entice them with the upcming event information.
If the query does not relate to the upcoming events or plans for the coming week, month or ask about one-off events reply "exclude" in the decision field.
<|im_end|>
<|im_start|>assistant
<think>
Alright, let's break down the query: "Do you offer any packages for group bookings or private events?" The user is asking about packages for group bookings or private events.
First, I need to check which document handles this information. The guidelines mention that reservations are covered in the Reservations Document, which includes details on group bookings and private events. The Upcoming Events Document only lists public events like special occasions, weekly/monthly happenings, and doesn't handle private event packages.
The query here is specifically about group bookings and private events, which according to the crossover topics, is the responsibility of the Reservations Document. Since the Upcoming Events Document doesn't include information on private event packages or group booking policies, including it here wouldn't help answer the user's question. Therefore, the decision is to exclude the Upcoming Events Document.
</think>
{
"reasoning": "The query asks about group booking packages and private events. The upcoming events document does not handle private event packages or group reservation policies, which are covered by the reservations document. Since the query relates to booking logistics rather than public events listed in the upcoming events document, excluding it from the context is appropriate.",
"decision": "exclude"
}
<|im_end|>
|
End of preview. Expand
in Data Studio
README.md exists but content is empty.
- Downloads last month
- 3