text
stringlengths 7.77k
10.6k
|
|---|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜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"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜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"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜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"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜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"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜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"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜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"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜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"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜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"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜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"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜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"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜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"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜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"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜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"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜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"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜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"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜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"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜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"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜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"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜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"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜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"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜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"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜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"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜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"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜Assistant｜>
<think>
Okay, let's look at the user's query: "Are there group booking or private event packages available?"
Now, I need to determine if the upcoming events document is relevant here. The upcoming events document contains information about special one-off events, weekly/monthly events, and their details like dates, tickets, descriptions, etc. It's mainly for public events that customers can attend, not for private bookings.
The user is asking about group bookings and private event packages. From the guidelines, private events and group bookings are handled by the reservations document, not the upcoming events document. The reservations document includes policies on how groups and large bookings are handled, minimum spends, and other reservation details.
The crossover topics section also mentions that queries about group bookings are handled by the reservations document. Since the upcoming events document doesn't cover private event packages or group booking policies, including it wouldn't help answer the user's question. Therefore, the decision should be to exclude the upcoming events document here.
</think>
{
"reasoning": "The query specifically asks about group booking or private event packages. According to the guidelines, private events and group bookings are handled by the reservations document, not the upcoming events document. The upcoming events document only lists public events and does not contain information about booking packages, group policies, or private event arrangements. Therefore, the upcoming events document is irrelevant for this query.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜Assistant｜>
<think>
Okay, let's break down the user's query: "Can I arrange a private event or group booking with a customized package?" The user is asking about organizing a private event or group booking with a custom package.
First, I need to check what each document covers. The upcoming events document includes info on special one-off events, weekly/monthly events, and public events like live music or comedy nights. Private events and group bookings aren't listed there. Instead, the reservations document handles group bookings, private events, and reservation policies. Additionally, customized packages would likely involve venue facilities and policies, which are covered in the venue information document.
Since the query is about arranging a private event or group booking, which falls under reservations and venue information, the upcoming events document isn't relevant here. The events document is for public events, not private bookings. Therefore, excluding the upcoming events document makes sense as the answer will come from other documents.
</think>
{
"reasoning": "The query asks about arranging a private event or group booking with a customized package. This type of request pertains to reservation policies, venue capacity, facilities, and booking processes, which are all covered in the reservations and venue information documents. The upcoming events document does not include information about private bookings or group reservation logistics, as it focuses solely on publicly accessible events like one-off specials, weekly/monthly events, or venue-hosted experiences. Therefore, the upcoming events document is not relevant to this query.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜Assistant｜>
<think>
Okay, let me go through this step by step. The user is asking about special packages for group bookings or private events. First, I need to check which document handles this type of query. The task says to decide if the upcoming events document is relevant.
The upcoming events document includes one-off, weekly, or monthly events that are open to the public. It has details like dates, tickets, and descriptions. But group bookings and private events aren't listed there. Those are handled by the reservations document, which covers reservation policies, group handling, and how to make bookings.
The query specifically mentions group bookings and private events, which fall under the reservations document's scope. Since the upcoming events document doesn't handle private events or group packages, including it here isn't necessary. Therefore, I should exclude the upcoming events document because the answer lies in the reservations document instead.
</think>
{
"reasoning": "The query asks about special packages for group bookings or private events. According to the guidelines, private events and group bookings are handled by the reservations document, not the upcoming events document. The upcoming events document only covers public events like one-off or recurring activities (e.g., live music, workshops). Since the query pertains to reservations and group policies, the upcoming events document is irrelevant here.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking about group bookings and private events with tailored packages. First, I need to check where such information would be located according to the given guidelines.
The upcoming events document covers public events like special one-offs, weekly, or monthly events. However, the query here is about group bookings and private events, which are more about reservations and venue policies.
Looking at the crossover topics, the reservations document handles group bookings, private events, and reservation policies. The venue information document might have details on capacity and facilities, which are relevant for tailored packages. The query isn't about public events but about organizing private ones, so the upcoming events document isn't the right source here.
According to the guidelines, private events and space rentals are handled by the reservations document, not the upcoming events. Therefore, the upcoming events document should be excluded from the context for this query.
</think>
{
"reasoning": "The query asks about group bookings and private events with tailored packages, which falls under reservation policies and venue capacity information. According to the guidelines, private events and group booking logistics are handled by the reservations document, not the upcoming events document. The upcoming events document does not contain information about booking processes, tailored packages, or private event arrangements, as it only lists public events (special, weekly, or monthly). Therefore, including this document would not help answer the query.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking about special packages for private events or group reservations. I need to check if the upcoming events document is relevant here.
First, according to the guidelines, private events and group bookings are handled by the reservations document, not the upcoming events. The events document is about public events like live music or comedy nights.
The query is specifically about packages for private events or group reservations. That's about booking spaces or arranging group services, which falls under the reservations document's info on how groups and large bookings are handled, including policies and minimum spends.
The upcoming events document doesn't cover private bookings. It's for one-off or recurring public events. So including it here wouldn't help answer the user's question. The right info is in the reservations doc, so exclude the events doc.
</think>
{
"reasoning": "The query asks about special packages for private events or group reservations, which pertains to reservation policies and group handling procedures. This information is covered in the reservations document, which includes details on group bookings, minimum spends, and reservation management. The upcoming events document specifically covers public-facing events like workshops or themed nights, not private event packages or reservation logistics. Therefore, the upcoming events document is not relevant to answering this query.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜Assistant｜>
<think>
Okay, let's analyze this query. The user is asking about booking a private event or a group gathering with a special package deal. First, I need to check what each document covers. The upcoming events document includes special one-off events, weekly, and monthly events open to the public, along with their details like dates and tickets.
However, the query is about organizing a private event or group booking, which falls under reservations. According to the guidelines, private events and space rentals are handled by the reservations document, not the upcoming events. The upcoming events document is only for public events. Since the user's request is about booking their own event, the reservations document would have the necessary info on policies, group handling, and package deals. Therefore, the upcoming events document isn't relevant here and should be excluded.
</think>
{
"reasoning": "The query about booking a private event or group gathering with a special package deal relates to reservations and venue policies for organized group bookings. The upcoming events document specifically covers public-facing events like weekly/monthly programming, special one-off experiences, and event-specific rules. Private event bookings fall under reservations and venue capacity/amenities details, which are handled by the reservations and venue information documents. Since the query focuses on organizing a private event rather than attending a pre-scheduled public event, the upcoming events document does not contain relevant information.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜Assistant｜>
<think>
Okay, let's tackle this query step by step. The user is asking, "Do you offer exclusive packages for group bookings or private events?" 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, their dates, times, ticket info, descriptions, and policies. It's about public events like live music, comedy nights, or special occasions like New Year's Eve.
Now, the query is about exclusive packages for group bookings or private events. Group bookings and private events typically relate to reservations, not public events. The reservations document covers policies for groups, minimum spends, cancellations, and how to make reservations. The venue information document might handle details about capacity and facilities for private events.
Crossover topics mention that group bookings and private events are handled by the reservations and venue info documents. The upcoming events document only deals with public events. Since the user is asking about exclusive packages for groups or private functions, this falls under reservations and venue info, not the upcoming events. Therefore, the upcoming events document should be excluded.
</think>
{
"reasoning": "The query asks about exclusive packages for group bookings or private events, which pertains to reservation policies and venue facilities rather than public events listed in the upcoming events document. The reservations and venue information documents handle group bookings, private events, and package details, making the upcoming events document irrelevant here.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜Assistant｜>
<think>
Alright, let's start by understanding the user's query. They're asking about customizable packages for group bookings or private events. Now, I need to check which document handles this information.
First, I recall that the Upcoming Events Document includes one-off events, weekly or monthly happenings, like live music or special holiday events. It doesn't cover private event packages or group bookings.
Looking at the Crossover Topics, the Reservations Document handles group bookings, private events, and reservation policies. The query is about customizable packages for these, which falls under how the venue manages reservations and group services.
Since the question is about organizing private events or group bookings, which is handled by the Reservations Document, the Upcoming Events Document isn't relevant here. There’s no mention of events open to the public in the query. Therefore, I should exclude the Upcoming Events Document.
</think>
{
"reasoning": "The query asks about customizable packages for group bookings or private events. This type of information pertains to reservation policies, group handling, and event-specific arrangements, which are explicitly covered in the reservations document under 'how groups and large bookings are handled' and 'detailed information on seating layouts'. The upcoming events document does not include details about private events, group booking policies, or customizable packages, as it focuses on public-facing events (e.g., weekly/monthly activities, special one-off events). Since the query aligns with the reservations document's scope, the upcoming events document is not relevant here.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜Assistant｜>
<think>
Okay, let's analyze the query here. The user is asking, "Can I reserve a private event or group booking with a unique package?"
First, I need to determine which document would contain the information relevant to this query. The Upcoming Events document includes special one-off events, weekly/monthly events, and details like dates, tickets, descriptions. But private events and group bookings aren't listed there. Instead, according to the guidelines, private events and group bookings are handled by the Reservations document. The Crossover Topics section clearly states that group bookings and private events fall under the Reservations document.
The Upcoming Events document is for public events, not private reservations. Since the query is about reserving a private event or group booking, the relevant info would be in the Reservations document, not Upcoming Events. Therefore, the decision should be to exclude the Upcoming Events document from the context.
</think>
{
"reasoning": "The query about reserving a private event or group booking pertains to reservation policies and handling of group bookings, which are explicitly covered in the reservations document. The upcoming events document does not contain information about private events, space rentals, or reservation logistics—it only lists public events. Therefore, the upcoming events document is irrelevant for this query.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜Assistant｜>
<think>
Okay, let me break down the query: "Do you have any event packages for group bookings or private events?" The user is asking about packages for group bookings or private events.
First, I need to check what each document covers. The upcoming events document includes info on special one-off events, weekly/monthly events, ticketing, and policies specific to those events. However, group bookings and private events are mentioned in the guidelines as being handled by the reservations document. The reservations document covers how groups and large bookings are handled, including policies on minimum spends, time limits, and cancellation.
The query is specifically about event packages for groups or private events. Since private events and group bookings aren't listed in the upcoming events document but are in the reservations document, the upcoming events document isn't relevant here. The venue information document might have capacity details, but the actual packages and booking policies are in reservations. Therefore, the upcoming events document should be excluded because the answer is found elsewhere.
</think>
{
"reasoning": "The query asks about event packages for group bookings or private events. The upcoming events document does not contain information about group booking packages or private event arrangements, as these are handled by the reservations document. The reservations document covers policies, minimum spends, and processes for group bookings and private events. Since the query pertains to services managed by the reservations document, the upcoming events document is not relevant here.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking about specific packages for private events or group bookings. First, I need to check what each document covers. The upcoming events document includes one-off events, weekly/monthly happenings, and their details. But the query here is about private events and group bookings, which from the guidelines, I remember are handled by the reservations document. The reservations document covers how groups and large bookings are managed, including reservation policies and packages. Since the user's question is related to group bookings and private event packages, that's exactly what the reservations document is for. The upcoming events document doesn't deal with private events or group packages—those are public events. Therefore, the upcoming events document isn't relevant here. So, the decision should be to exclude it.
</think>
{
"reasoning": "The query asks about specific packages for private events or group bookings. The upcoming events document only contains information about public events (special one-offs, weekly/monthly events) and does not handle private event packages or group booking policies. These topics are explicitly covered in the reservations document, which details group booking handling, reservation policies, and venue capacity. Since the query pertains to services managed by the reservations document and not public events, the upcoming events document is irrelevant for this context.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜Assistant｜>
<think>
Okay, let's see. 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, weekly/monthly events, things like live music, comedy nights, etc. It's for public events. But the query here is about group bookings and private events.
Looking at the Crossover Topics, the Reservations Document handles group bookings, private events, and package deals. The guidelines mention that private events and space rentals are handled by Reservations, not Upcoming Events.
So even though the user mentions "package deal," that's more about booking and reservations policies rather than public events. The Upcoming Events Document doesn't cover private bookings. Therefore, the answer should rely on the Reservations Document, excluding the Events Document.
</think>
{
"reasoning": "The query asks about package deals for group bookings or private events. The upcoming events document does not cover private events or group booking policies, which are handled by the reservations document. Since the query pertains to reservations and private event packages, the upcoming events document is not relevant and should be excluded.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking about special event packages for private gatherings or group bookings. I need to determine if the upcoming events document is relevant here.
First, looking at the contents of the upcoming events document, it includes one-off events like live music, comedy nights, workshops, and special occasions like New Year's Eve. It also covers weekly and monthly events open to the public. However, the query is about private events and group bookings, which are handled by the reservations document based on the crossover topics mentioned.
The guidelines state that private events and space rentals aren't covered in the upcoming events document. Instead, reservations document handles group bookings, policies, and how to make reservations. Since the user is asking about packages for private gatherings, this falls under reservations, not public events. Therefore, the upcoming events document doesn't contain the necessary information and should be excluded.
</think>
{
"reasoning": "The query asks about special event packages for private gatherings or group bookings. The upcoming events document primarily contains information about public events such as live music, comedy nights, or seasonal celebrations. Private gatherings and group booking policies, including packages and logistics, are covered in the reservations document, which handles reservation policies, minimum spends, and group-specific details. Since the query pertains to private event organization and policies, the upcoming events document does not contain relevant information required to address the user's request.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking about private event or group booking packages for large groups. I need to check if this falls under the upcoming events document.
The upcoming events document includes special one-off events, weekly or monthly events, like concerts or holiday celebrations. It also mentions event-specific details like dates, tickets, and policies. However, group bookings and private events are handled by the reservations document. The guidelines clearly state that private events and space rentals are not covered in the upcoming events document. Instead, reservations handle how groups and large bookings are managed, including policies and reservation procedures.
Since the query is about group bookings and private events, which relate to reservation policies and how the venue accommodates large groups, the answer lies in the reservations document. There's no mention of events that are open to the public here. Therefore, the upcoming events document isn't relevant here. Excluding it makes sense because the information needed is elsewhere.
</think>
{
"reasoning": "The query asks about private event or group booking packages for large groups. According to the guidelines, private events and space rentals are handled by the reservations document, not the upcoming events document. The upcoming events document focuses on public events like one-off or recurring activities (e.g., live music, workshops), not private bookings. Since the query pertains to group reservations and venue policies for large bookings, the reservations document is the appropriate context, making the upcoming events document irrelevant here.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜Assistant｜>
<think>
Okay, let me process this query. The user is asking about event packages for private or group bookings. First, I need to check if the upcoming events document contains information relevant to this.
From the guidelines, the upcoming events document covers public events like special one-offs, weekly, or monthly events. However, private events and group bookings are handled by the reservations document. The query specifically mentions private or group bookings, which fall under the reservations document's responsibility. The events document doesn't include private event packages or group booking policies.
Also, the crossover topics mention that group bookings are handled by the reservations document. Since the query is about availability of packages for such bookings, the upcoming events document isn't needed here. The answer would rely on the reservations document's details on handling groups and reservations policies. Therefore, I should exclude the events document.
</think>
{
"reasoning": "The query asks about event packages for private or group bookings, which pertains to reservation policies and group handling. The upcoming events document does not cover private events, space rentals, or group booking logistics, as these are explicitly managed by the reservations document. Since the query focuses on packages for bookings rather than public event details, the upcoming events document is irrelevant here.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜Assistant｜>
<think>
Okay, let's look at this query: "Do you offer any promotions or packages for group or private event bookings?" The user is asking about promotions or packages specifically for group bookings or private events.
First, I need to check what's covered in the Upcoming Events Document. According to the guidelines, that document includes special one-off events, weekly or monthly events, things like live music, comedy nights, or workshops. It also includes event-specific details like dates, tickets, and policies related to those specific events. However, private events or group bookings aren't part of the Upcoming Events Document.
The Crossover Topics mention that reservations and group bookings are handled by the Reservations Document. The query here is about promotions or packages for such bookings, which would involve reservation policies, minimum spends, group handling—all covered in Reservations. The Upcoming Events Document doesn't deal with private events or group packages; it's more about public events the venue hosts.
Also, the Guidelines state that queries about private events or space rentals are handled by the Reservations Document, not Upcoming Events. Since the user is asking about group/private event promotions, this clearly falls under Reservations. The Upcoming Events Document only includes public events. Therefore, including it here wouldn't help answer the query.
So the decision should be to exclude the Upcoming Events Document because the query is about group bookings and promotions handled by the Reservations Document.
</think>
{
"reasoning": "The query is seeking information about promotions or packages for group or private event bookings. The Upcoming Events Document does not contain information related to group bookings, private events, or venue packages; these topics are covered by the Reservations Document. Since the query does not pertain to public events, special occasions, or venue-hosted activities listed in the Upcoming Events Document, excluding it ensures the context remains focused on the relevant reservation policies and group booking details.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜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.
<｜Assistant｜>
<think>
Okay, let me start by breaking down the user's query. They're asking about booking a group event or private gathering with a package deal. The task here is to determine if the upcoming events document is relevant for answering this.
First, I need to recall what's in the upcoming events document. It lists special one-off events, weekly/monthly events, details like dates, times, tickets, and event descriptions. It's for public events like live music, comedy nights, workshops, or special occasions like New Year's. But private events or bookings aren't covered here.
The query mentions group bookings and package deals. According to the guidelines, reservations and group bookings are handled by the reservations document. The upcoming events document is more about public events, not private gatherings. Even if there's a package deal mentioned, that likely relates to reservation policies, which the reservations document would cover.
The crossover topics specify that group bookings and private events fall under the reservations document. So since the user's question is about arranging a private group event, the upcoming events document isn't needed. The answer would be in the reservations info, not the events. Therefore, the decision is to exclude the upcoming events document.
</think>
{
"reasoning": "The user's query pertains to booking a group event or private gathering with a package deal. This type of request falls under group bookings and private event policies, which are explicitly covered in the reservations document. The upcoming events document does not include information about private gatherings, package deals, or reservation policies, as it focuses on public events like live music, workshops, or special occasions. Since the query is about logistics for organizing a private event rather than details about public events, the upcoming events document is not relevant here.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any group booking packages or private event deals 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.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking about group booking packages or private event deals. The task is to decide if the upcoming events document is relevant here.
First, I need to recall what's in the upcoming events document. It includes special one-off events, weekly/monthly recurring events, details like dates, tickets, and descriptions. Rules and policies specific to those events are there too. But group bookings and private events are handled by the reservations document, not the events document.
The query is specifically about group packages and private deals. According to the guidelines, private events and space rentals aren't covered in the upcoming events doc. Those are the reservation document's responsibility. The events doc is for public events. Since the user is asking about group bookings or private deals, the reservations document would have the info on how they handle large groups, minimum spends, reservation policies, etc.
Also, the crossover topics mention that reservations handle group bookings. The upcoming events doc doesn't include anything about booking packages or private events. So including it here wouldn't help answer the user's question.
Therefore, the decision should be to exclude the upcoming events document. The reasoning is that the query relates to group bookings and private events, which are under the reservations document's scope, not the upcoming events.
</think>
{
"reasoning": "The query asks about group booking packages and private event deals, which pertain to reservations and venue policies rather than specific upcoming events. The reservations document handles details on group bookings, private events, and related policies. The upcoming events document only contains information about public events, not reservations or private event packages. Therefore, it is excluded from the context for this query.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you offer any private event or group booking specials or 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.
<｜Assistant｜>
<think>
Okay, let me break this down. The user is asking about private event or group booking specials or packages. The task is to decide if the upcoming events document should be included.
First, I need to check what's in the upcoming events document. It covers special one-off events, weekly/monthly events, including details like dates, tickets, and descriptions. Private events and group bookings aren't mentioned there. Instead, the reservations document handles group bookings, private events, and policies related to that.
The guidelines say that queries about private events or space rentals are handled by the reservations document, not the upcoming events. Since the user is asking about group booking packages, which would involve reservation policies, minimum spends, and how large groups are managed, that's all in the reservations document. The upcoming events document doesn't cover private bookings or group specials. Therefore, excluding the upcoming events document makes sense here because the answer lies elsewhere.
</think>
{
"reasoning": "The query asks about private event or group booking specials/packages. According to the guidelines, private events and group bookings are handled by the reservations document, not the upcoming events document. The upcoming events document focuses on public events like one-off or recurring activities, whereas group booking policies, pricing, and logistics are covered in the reservations document. Since the query does not relate to public events or event details (e.g., dates, tickets) but instead to group-specific reservations, the upcoming events document is irrelevant here.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I arrange a group event or private party with a tailored 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.
<｜Assistant｜>
<think>
Okay, let's tackle this query. The user is asking if they can arrange a group event or private party with a tailored package. First, I need to check what each document covers.
The upcoming events document includes one-off, weekly, or monthly public events like special occasions or workshops. It doesn't handle private events or group bookings.
Looking at the crossover topics, group bookings and private parties fall under the reservations document. That document specifically addresses how groups and large bookings are handled, including reservation policies, minimum spends, and tailored packages.
Since the query is about organizing a private event or group booking, the answer would be found in the reservations document, not the upcoming events one. Therefore, the upcoming events document isn't needed here. The decision should be to exclude it.
</think>
{
"reasoning": "The query about arranging a group event or private party with a tailored package pertains to reservations, group booking policies, and tailored packages. This type of request is explicitly covered by the reservations document, which details how group bookings are handled, reservation policies, and minimum spends. The upcoming events document focuses on public events, workshops, or special occasions open to the public, not private group bookings or venue rental logistics. Therefore, the upcoming events document does not contain relevant information for this query.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you have special 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.
<｜Assistant｜>
<think>
Okay, let's break down this query. The user is asking about special event packages for group bookings or private events. The task is to decide if the upcoming events document should be included.
First, looking at what's in the upcoming events document: it's about public events like weekly/monthly happenings, one-off special events like New Year's, live music, etc., along with their dates, tickets, and policies. But the query here is about group bookings and private events.
Now, checking the crossover topics. The reservations document handles group bookings, large parties, private events, and details about minimum spends, reservations, and policies. The venue info document might have capacity and facilities, but the actual packages and booking process are in reservations.
The guidelines say that private events and group bookings are handled by the reservations document, not the upcoming events one. Since the user is specifically asking about packages for these, the answer would come from the reservations document. The upcoming events document doesn't cover private bookings, so it should be excluded.
</think>
{
"reasoning": "The query asks about special event packages for group bookings or private events. According to the guidelines, private events and group bookings are handled by the reservations document, not the upcoming events document. The upcoming events document only includes public events like weekly/monthly activities or one-off experiences. Since the query pertains to group/private event packages (a reservations-related topic), the upcoming events document is irrelevant here.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there package deals for hosting private events or group gatherings?
### 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.
<｜Assistant｜>
<think>
Alright, let me break this down. The user is asking about package deals for private events or group gatherings. First, I need to check what each document covers. The upcoming events document includes special one-off, weekly, and monthly events open to the public, like live music or holiday celebrations. Private events and group bookings aren't part of that. The reservations document handles group bookings, private events, and details about reservations, including policies and packages. Since the query is about package deals for private events, that falls under the reservations document, not upcoming events. Therefore, the upcoming events document should be excluded because it doesn't handle private event packages.
</think>
{
"reasoning": "The query specifically asks about package deals for hosting private events or group gatherings. Private events and space rentals are explicitly mentioned in the guidelines as being handled by the reservations document, not the upcoming events document. The upcoming events document only covers public events (e.g., live music, workshops, holiday celebrations) and does not include information on private group packages. Therefore, including the upcoming events document would not help answer the query, as the relevant details reside in the reservations document.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I reserve a package for a group event or private gathering?
### 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.
<｜Assistant｜>
<think>
Okay, let me see. The user is asking if they can reserve a package for a group event or private gathering. The task is to decide if the upcoming events document is relevant here.
First, looking at the contents of the upcoming events document, it includes special one-off events, weekly and monthly events, with details like dates, tickets, and descriptions. It doesn't cover reservations or group bookings.
The query is about reserving a package for a group, which falls under reservations policies and how the venue handles group bookings. According to the guidelines, group bookings and private events are handled by the reservations document, not the upcoming events. Even though the user mentions a "package," that's likely about reservations, space rental, or private gatherings, which are covered in the reservations doc.
The crossover topics mention that reservations, including group handling and private events, are in the reservations document. The upcoming events document only has public events. Since the query is about group reservations, the upcoming events document isn't needed. So the decision should be exclude.
</think>
{
"reasoning": "The query is about reserving a package for a group event or private gathering, which pertains to group booking policies and reservation logistics. The upcoming events document does not cover reservations, private gatherings, or group booking packages—these topics are explicitly handled by the reservations document. Since the query focuses on booking actions and policies rather than event details (like dates, descriptions, or ticketing for public events), the upcoming events document is irrelevant here.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there exclusive 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.
<｜Assistant｜>
<think>
Okay, let me try to figure out whether the Upcoming Events document should be included for this query. The user is asking about exclusive packages for private events or group reservations.
First, I need to recall what's in the Upcoming Events document. According to the guidelines, it includes special one-off events, weekly events, and monthly events that are open to the public. These could be things like live music nights, comedy shows, or holiday celebrations. The document also has details like dates, times, tickets, and event descriptions.
Now, the query is about private events and group reservations. The crossover topics mention that private events and group bookings are handled by the Reservations document. The Reservations document covers policies for group bookings, minimum spends, cancellation policies, and how to make reservations.
The user isn't asking about attending a public event; they're interested in booking a private event or group reservation. Since the Upcoming Events document only lists public events and doesn't handle private bookings, the information needed for this query would be in the Reservations document instead.
Additionally, the guidelines explicitly state that private events and space rentals are not covered in the Upcoming Events document. Therefore, including it here wouldn't help answer the user's question. The correct document to reference here is Reservations, so the decision should be to exclude the Upcoming Events document.
</think>
{
"reasoning": "The query asks about exclusive packages for private events or group reservations. The upcoming events document does not cover private events or group reservations, as these are handled by the reservations document. Private events and group booking policies, including exclusive packages, fall under the reservations document's scope, which details reservation policies, group handling, and related charges. The upcoming events document only pertains to public events, special occasions, or scheduled activities open to general attendees, none of which are directly relevant to private event packages or group reservation inquiries.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you have any package deals for booking private events or group gatherings?
### 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.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking about package deals for private events or group gatherings. I need to check if the upcoming events document is relevant here.
The upcoming events document includes one-time events, weekly/monthly happenings, and their details. But private events and group bookings are handled by the reservations document, which covers policies, minimum spends, and how to book. The query is about packages for private events, which isn't listed under the upcoming events contents. So, the reservations document is the right source here. Therefore, the upcoming events doc should be excluded.
</think>
{
"reasoning": "The query asks about package deals for booking private events or group gatherings. This falls under the reservations document, which handles group bookings, policies, and reservation procedures. The upcoming events document does not contain information on private event packages or group booking deals, as it focuses on public events like special occasions, weekly/monthly activities, and one-off experiences. Since the query pertains to services managed by the reservations document, the upcoming events document is not relevant here.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I host a private event or group booking with a customized 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.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking about hosting a private event or group booking with a customized package. I need to figure out which document handles this.
The upcoming events document covers special one-off, weekly, or monthly events open to the public. But the query is about a private event, which isn't listed there. Private bookings and group reservations are mentioned in the CROSSOVER TOPICS as handled by the reservations document. The reservations document includes info on how groups and large bookings are managed, policies, and how to make reservations.
The guidelines say that private events and space rentals are not in the upcoming events doc but are handled by reservations. So even though the user is asking about a customized package, that's part of reservations, not events. Therefore, the upcoming events document isn't needed here.
Final decision: exclude.
</think>
{
"reasoning": "The query pertains to hosting a private event or group booking with a customized package deal. These topics fall under group reservations, private event policies, and customized arrangements, which are explicitly covered in the reservations document. The upcoming events document only contains information about public events (one-off, weekly, or monthly) and does not include details about private bookings, group reservations, or package deals. Since the query is unrelated to public events, the upcoming events document is not relevant and should be excluded.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you offer any group booking or private event promotions?
### 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.
<｜Assistant｜>
<think>
Okay, let's analyze the query: "Do you offer any group booking or private event promotions?"
The user is asking about group bookings or promotions for private events. According to the guidelines, private events and group bookings are handled by the reservations document, not the upcoming events document. The upcoming events document only lists public events like special occasions, weekly/monthly events, or one-off experiences.
Since the query is about group booking policies and promotions, which fall under reservations and possibly venue information (for capacity and facilities), the upcoming events document isn't relevant here. The crossover topics mention that group bookings are handled by the reservations document. Therefore, including the events document wouldn't help answer the query, so the decision should be to exclude it.
</think>
{
"reasoning": "The query asks about group booking or private event promotions. The upcoming events document does not handle private events or group booking policies, which are covered by the reservations document. Since the query pertains to promotions for group bookings (reservations domain) rather than public events listed in the upcoming events document, the latter is not relevant to answering this query.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any group event or private gathering 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.
<｜Assistant｜>
<think>
Okay, let's see. The user is asking about group events or private gathering packages. The task is to decide if the upcoming events document is relevant here.
First, checking the contents of the upcoming events document. It includes special one-off events, weekly/monthly events, dates, tickets, descriptions, and policies specific to those events. But the query is about group packages and private gatherings.
Looking at the crossover topics, the reservations document handles group bookings, large reservations, and private events. The guidelines say that private events and space rentals are covered by the reservations document, not the upcoming events. Since the user's query is about group packages, which would involve reservation policies and how the venue handles large bookings, the answer should come from the reservations document.
The upcoming events document doesn't include private event packages, only public events. Therefore, the upcoming events document isn't needed here. So the decision is to exclude it.
</think>
{
"reasoning": "The query asks about group event or private gathering packages, which pertains to reservation policies and handling of large bookings. According to the guidelines, private events and space rentals are managed by the reservations document, not the upcoming events document. The upcoming events document focuses on public events, not private group packages.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I book a private event or group gathering with an event 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.
<｜Assistant｜>
<think>
Okay, let's analyze the query: "Can I book a private event or group gathering with an event package?" The user is asking about booking a private event or group gathering, which involves reservations and event packages.
First, I need to check what each document covers. The upcoming events document includes one-off, weekly, and monthly events that are open to the public, like special occasions or live music. Private events and group bookings aren't part of this document.
The reservations document handles reservations, group bookings, and policies related to private events. Since the query is about booking a private event, it's covered by the reservations document, not the upcoming events. The events document doesn't handle private bookings or packages; those are managed through reservations.
Therefore, the upcoming events document doesn't contain information relevant to private bookings. The correct document to include here is the reservations document. So, the decision should be to exclude the upcoming events document.
</think>
{
"reasoning": "The query is about booking a private event or group gathering with an event package. Private events and group bookings are handled by the reservations document, which includes policies, packages, and procedures for such requests. The upcoming events document only covers publicly accessible events (e.g., live music, workshops) and does not contain information about private bookings or event packages. Therefore, the upcoming events document is not relevant to this query.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you offer specific event packages for group or private 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.
<｜Assistant｜>
<think>
Okay, let me break this down. The user is asking if the venue offers specific event packages for group or private bookings. I need to determine if the upcoming events document is relevant here.
First, looking at what's in the upcoming events document: it covers one-off events like live music, comedy nights, or special occasions, along with their dates, tickets, and policies. The reservations document, on the other hand, handles group bookings, private events, and reservation policies.
The query is about event packages for groups or private bookings. That sounds like it's about organizing a private event or booking a space for a group. According to the guidelines, private events and space rentals are handled by the reservations document, not the upcoming events. The upcoming events are public, not private. So the reservations document would have the info on group packages, not the events document.
Also, the crossover topics mention that group bookings are under reservations. Since the user's question is specifically about event packages for groups or private bookings, the upcoming events document isn't needed here. The answer would come from the reservations document. Hence, exclude the events document.
</think>
{
"reasoning": "The query asks about event packages for group or private bookings. The upcoming events document does not cover private bookings or group reservations, as these are handled by the reservations document. Private events and space rentals are explicitly excluded from the upcoming events document's scope, which only details public events. Therefore, the upcoming events document is not relevant to this query.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any group booking or private event packages for special occasions?
### 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.
<｜Assistant｜>
<think>
Okay, let's start by understanding the user's query. They're asking about group booking or private event packages for special occasions. First, I need to figure out which document would contain the relevant information.
The upcoming events document includes one-off events like workshops, live music, or special occasions like New Year's Eve. It also has weekly or monthly recurring events, but private events aren't part of that. Private event packages and group bookings are more about reserving space or arranging services, which falls under the reservations document.
Looking at the crossover topics, the reservations document specifically handles group bookings, reservation policies, and private events. The user isn't asking about attending a public event but rather organizing their own private one. Therefore, the query should be directed to the reservations document, not the upcoming events.
Since the upcoming events document doesn't cover private bookings, the correct decision is to exclude it. The reasoning here is that the reservations document is the appropriate source for group or private event packages.
</think>
{
"reasoning": "The query is about group booking or private event packages, which are handled by the reservations document. The upcoming events document only contains information about public events, special one-off events, or recurring weekly/monthly activities. Since private event packages and group bookings relate to reservation policies and space allocation, they fall under the reservations document's scope. The upcoming events document does not include details about private bookings or group packages, making it irrelevant for this query.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you offer packages for private events or group bookings with food and drink options?
### 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.
<｜Assistant｜>
<think>
Okay, let's break down the user's query: "Do you offer packages for private events or group bookings with food and drink options?"
First, I need to figure out which document this relates to. The user is asking about private events or group bookings with food/drink packages. From the guidelines, private events and group bookings are handled by the reservations document. The upcoming events document is only for public events like special one-offs, weekly, or monthly events.
The query here is about organizing a private event or a group booking, which involves reservations, packages, and possibly minimum spends or policies. That's all covered in the reservations document. The upcoming events document doesn't include anything about private bookings or group packages. It's about public events. Since the user's question is about their own private booking, the upcoming events document isn't relevant here.
Also, the crossover topics mention that group bookings are handled by reservations. So the decision should be to exclude the upcoming events document because the answer is found elsewhere. The key point is that private events and group bookings are not part of the upcoming events content. Hence, exclude.
</think>
{
"reasoning": "The query asks about packages for private events or group bookings with food and drink options. This type of request pertains to reservations, policies for group bookings, and venue packages, which are covered in the reservations document. The upcoming events document does not contain information about private event packages, group booking logistics, or venue rental policies, as these fall under the reservations document's scope. Since the query focuses on booking and service packages rather than public events or special activities listed in the upcoming events document, the latter is irrelevant here.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I reserve a special package for a private event or group reservation?
### 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.
<｜Assistant｜>
<think>
Alright, let's break this down. The user is asking about reserving a special package for a private event or group reservation. First, I need to check if this falls under the Upcoming Events document.
Looking at the Upcoming Events document contents, it covers special one-off events, weekly, and monthly events that are open to the public. Private events and group reservations aren't listed there. The guidelines clearly state that private events and space rentals are handled by the Reservations document.
The query is specifically about group reservations and private events, which relates to policies on how groups are handled, minimum spends, and reservation procedures. All of that information is in the Reservations document. The Upcoming Events document doesn't handle private bookings, only public events. Therefore, including it here wouldn't provide relevant information for the user's request.
Since the answer is found in the Reservations document, the Upcoming Events document should be excluded. The decision is to exclude.
</think>
{
"reasoning": "The query asks about reserving a special package for private events or group reservations. This pertains to policies, terms, and logistics for group bookings, which fall under the reservations document. The upcoming events document focuses on public events (e.g., live music, workshops) and their details (dates, tickets, descriptions), not private reservations. Group/private event inquiries are explicitly handled by the reservations document, as noted in the guidelines.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you provide any special packages for hosting private or group 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.
<｜Assistant｜>
<think>
Okay, let's tackle this query. The user is asking if the venue provides special packages for hosting private or group events. First, I need to determine which document handles this.
The upcoming events document mentions one-off, weekly, or monthly events open to the public, like comedy nights or workshops. Private events and group bookings aren't listed here; they fall under reservations. The reservations document covers group handling, minimum spends, and reservation policies.
The query is about packages for private/group events, which is about booking and policies, not public events. So the reservations document is the right source. Therefore, the upcoming events document isn't needed here. Decision is exclude.
</think>
{
"reasoning": "The query asks about special packages for hosting private or group events. The upcoming events document only contains information about public events (e.g., weekly/monthly events, one-off experiences). Queries related to private group bookings, reservation policies, or venue capacity for events are handled by the reservations document, which covers group handling, minimum spends, and reservation-specific rules. Since the user's inquiry pertains to private/group event packages, this falls outside the scope of the upcoming events document and is addressed by the reservations document instead.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any all-inclusive 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.
<｜Assistant｜>
<think>
Okay, let's break down the query: "Are there any all-inclusive packages for group bookings or private events?" The user is asking about packages for group bookings or private events.
Looking at the guidelines, the key point here is that queries related to group bookings or private events are handled by the reservations document, not the upcoming events document. The upcoming events document includes info on public events like live music or workshops, not private bookings.
The reservations document covers policies on group bookings, minimum spends, and how to reserve areas. All-inclusive packages would likely involve pricing, reservations, and venue facilities, which fall under the venue information and reservations docs. Since the query is about group bookings and private events, it's outside the scope of the upcoming events document. Therefore, the decision is to exclude the upcoming events document here.
</think>
{
"reasoning": "The query asks about all-inclusive packages for group bookings or private events. According to the guidelines, private events and group bookings are handled by the reservations document, which covers policies, packages, and reservation details. The upcoming events document only pertains to public events like one-off or recurring activities open to the general public. Since the query focuses on group/private event packages, the upcoming events document does not contain relevant information and should be excluded.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I book a package for a group event or private gathering with catering options?
### 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.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking about booking a package for a group event or private gathering with catering options. First, I need to figure out which document handles group bookings. The guidelines mention that group bookings and private events are handled by the reservations document. The upcoming events document only includes public events like special occasions or weekly/monthly activities.
Looking at the crossover topics, the reservations document covers group handling, private gatherings, and catering policies. The query here is about booking a package, which involves reservations and possibly catering—both are under the reservations document. The upcoming events document doesn't deal with private events or bookings; it's more about public events. Since the user isn't asking about attending an event but rather organizing their own, the upcoming events document isn't relevant here. Therefore, the decision should be to exclude it.
</think>
{
"reasoning": "The query is about booking a group event or private gathering with catering options. This type of request pertains to reservations, group policies, and catering logistics, which are explicitly covered by the reservations document. The upcoming events document does not handle private gatherings or group bookings, as it focuses solely on public events like special occasions, weekly/monthly activities, or one-off experiences. Since the query does not involve information about public events, event schedules, or event-specific rules, the upcoming events document is irrelevant here.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you offer package deals for hosting corporate events or private gatherings?
### 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.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking about package deals for corporate events or private gatherings. First, I need to check which document would handle that. The query is about hosting events, which involves reservations, pricing packages, and possibly facilities. The venue information document covers facilities and amenities, which might be part of a package. The reservations document includes info on group bookings, minimum spends, and how large bookings are handled. The upcoming events document is for public events like live music or special nights, not private bookings. Since corporate or private events are about reservations and venue facilities, the upcoming events doc isn't needed here. So, exclude it.
</think>
{
"reasoning": "The query asks about package deals for corporate events or private gatherings, which pertains to reservation policies, group handling, and venue facilities. This information is covered in the Reservations and Venue Information documents. The Upcoming Events document only contains information on public events like special occasions, weekly/monthly events, and does not handle private bookings or corporate package deals. Therefore, the Upcoming Events document is irrelevant to this query.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any bundled packages available 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.
<｜Assistant｜>
<think>
Okay, let's tackle this query. The user is asking about bundled packages for group bookings or private events.
First, I need to check the contents of the upcoming events document. From the guidelines, this document includes special one-off events, weekly/monthly events, their dates, times, tickets, and policies. But the query is about group packages and private events.
The reservations document handles group bookings, private events, and details like minimum spends, time limits, etc. The venue information document covers seating capacity and facilities. The query is asking about packages, which likely involve pricing, reservations, and policies—all covered in the reservations or venue info docs, not upcoming events.
Since bundled packages for groups fall under reservations, the upcoming events document doesn't have that info. Also, private events aren't part of the upcoming events, which are public. So the decision is to exclude the upcoming events document.
</think>
{
"reasoning": "The query asks about bundled packages for group bookings or private events. The upcoming events document does not contain information related to group bookings, private events, or bundled packages. These topics are covered in the reservations document and venue information document instead. The events document focuses on public events, workshops, or special occasions, not logistical details for reservations or private events. Therefore, excluding the upcoming events document is appropriate here.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you have exclusive deals or packages for group bookings and 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.
<｜Assistant｜>
<think>
Okay, let me see. The user is asking about exclusive deals or packages for group bookings and private events. The task is to decide if the upcoming events document is relevant here.
First, I recall that the upcoming events document includes special one-off events, weekly/monthly happenings, and their details like dates, tickets, etc. It doesn't handle group bookings or private events. Those topics are covered in the reservations document.
The query specifically mentions group bookings and private events. According to the guidelines, private events and space rentals are handled by the reservations document, not the events one. Also, deals or packages for groups would be part of reservation policies, which are in the reservations document.
The upcoming events document is more about public events like live music or workshops. Since the user's question is about group bookings and private events, the reservations document is the right place. Therefore, the upcoming events document isn't needed here. So the decision is to exclude.
</think>
{
"reasoning": "The query asks about exclusive deals or packages for group bookings and private events. The upcoming events document does not contain information on group bookings, private events, or venue packages. These topics are explicitly covered in the reservations document, which handles policies, group arrangements, and private event logistics. The upcoming events document focuses on public events like special occasions, workshops, or recurring weekly/monthly activities, none of which are relevant to group booking packages or private event deals. Therefore, the document is excluded.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I book a private event or group reservation with a special package offer?
### 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.
<｜Assistant｜>
<think>
Okay, let me think through this. The user is asking about booking a private event or group reservation with a special package offer.
First, I need to check what's in the upcoming events document. That document covers special one-off, weekly, and monthly events open to the public, like live music or holiday parties. It includes details about dates, tickets, and event descriptions.
But the query here is about private bookings and group reservations with packages. According to the guidelines, private events and space rentals are handled by the reservations document, not the upcoming events. The reservations document includes policies on group bookings, minimum spends, and how to make reservations. Special package offers would relate to the venue's reservation policies and possibly their service charges or facilities, which are in the reservations or venue info documents.
Since the query isn't about public events but rather private group bookings and packages, the upcoming events document isn't relevant here. The answer should come from the reservations document. Therefore, I should exclude the upcoming events document.
</think>
{
"reasoning": "The query is about booking a private event or group reservation with a special package offer. This falls under group booking policies and package offerings, which are explicitly handled by the reservations document according to the guidelines. The upcoming events document only contains information about public events (special one-offs, weekly/monthly activities) and does not address private event logistics or reservation packages. Therefore, the upcoming events document is not relevant for this query.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you have event package options for hosting private or group gatherings?
### 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.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking about event package options for hosting private or group gatherings. I need to determine if the upcoming events document is relevant here.
First, the upcoming events document includes info on one-off, weekly, or monthly events that are open to the public, like live music, comedy nights, or special holiday events. It also details dates, tickets, and policies for those specific events.
The query is about private or group gatherings, which sounds more like booking a space or arranging a private event. According to the guidelines, private events and space rentals are handled by the reservations document, not the upcoming events document. The reservations doc covers group bookings, policies, and how to make reservations for such events.
Additionally, the user is asking about "event package options," which likely involves details on pricing, reservations, and facilities—all covered in the venue information and reservations documents. The upcoming events document doesn't include private event packages; it's for public events.
Since the query falls under group bookings handled by the reservations document, the upcoming events document isn't needed here. Therefore, the decision is to exclude it.
</think>
{
"reasoning": "The query asks about event package options for private or group gatherings. The upcoming events document contains information on public events like one-off special occasions, weekly/monthly happenings, and related policies. Private or group event hosting details, including package options, are handled by the reservations document, which covers group booking policies, minimum spends, and reservation procedures. Since private gatherings are not part of the upcoming events document's scope, it should be excluded.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there packages available for booking a group event or private function?
### 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.
<｜Assistant｜>
<think>
Okay, let's break down this query. The user is asking about packages for booking group events or private functions. First, I need to figure out which document handles this information. The upcoming events document covers things like one-off events, weekly or monthly happenings, including details like dates, times, and tickets. But group bookings or private functions—those are more about reservations and venue policies.
Looking at the crossover topics, the reservations document specifically mentions handling group and large bookings, minimum spends, and how to make reservations. The venue information document might have details on capacity and facilities, but the actual packages and booking procedures are in reservations. The query is about availability of packages, which would involve reservation policies and group handling, not the events themselves. Since the upcoming events document doesn't cover private functions or group booking packages, the correct decision is to exclude it.
</think>
{
"reasoning": "The query asks about group event packages or private function bookings, which pertain to reservation policies and group handling. The upcoming events document does not cover reservation policies, group bookings, or private functions—these are explicitly handled by the reservations document. Since the query is not about public events, event schedules, or event-specific details, the upcoming events document is irrelevant here.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you offer any discount 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.
<｜Assistant｜>
<think>
Okay, let me think through this. The user is asking about discount packages for group bookings or private events. First, I need to check if the upcoming events document contains any information related to discounts for groups or private events.
Looking at the contents of the upcoming events document, it includes special one-off events, weekly events, and monthly events, along with details like dates, times, tickets, and event descriptions. It doesn't mention anything about pricing, discounts, or policies for group bookings or private events.
The reservations document, on the other hand, handles group bookings, private events, and related policies like minimum spends, time limits, and cancellation policies. Discount packages for groups would fall under the reservations document because it's about how the venue manages reservations and group services, not about specific events listed in the upcoming events.
Additionally, the guidelines state that private events and space rentals are covered by the reservations document, not the upcoming events. Since the query is about discounts for groups or private events, the relevant information would be in the reservations document. Therefore, the upcoming events document isn't needed here. Exclude it.
</think>
{
"reasoning": "The query asks about discount packages for group bookings or private events. The upcoming events document does not contain information on pricing, discounts, or policies related to group reservations or private events, as these are handled by the reservations document. Group bookings and private event logistics fall under reservation policies and service charges, which are explicitly covered in the reservations and venue information documents, not in the context of upcoming public events.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I arrange a group event or private gathering with a special offer 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.
<｜Assistant｜>
<think>
Okay, let's tackle this query. The user is asking if they can arrange a group event or private gathering with a special offer package. I need to determine if the upcoming events document is relevant here.
First, the upcoming events document covers special one-off events, weekly, and monthly events that are open to the public, like live music or holiday celebrations. But the query is about organizing a private group event or gathering, which isn't listed in the upcoming events. Instead, group bookings and private events are handled by the reservations document, which includes details on policies, minimum spends, and how to make reservations. Special offer packages for such events would likely be part of the reservation policies or maybe the menu's special offers, not the public events listed in the upcoming events doc. Since the user is inquiring about arranging their own event, not attending a public one, the upcoming events document isn't needed here. So, exclude it.
</think>
{
"reasoning": "The query is about arranging a group event or private gathering with a special offer package. This falls under group bookings and private events, which are explicitly handled by the reservations document, not the upcoming events document. The upcoming events document focuses on public events like one-off experiences, weekly/monthly activities, and special occasions open to the general public. Since the user is inquiring about organizing their own event rather than attending a pre-scheduled public event, the upcoming events document does not contain relevant information for this request.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you offer customized packages for group bookings or private gatherings?
### 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.
<｜Assistant｜>
<think>
Okay, let's analyze the query: "Do you offer customized packages for group bookings or private gatherings?" The user is asking about group bookings or private gatherings, specifically if there are customized packages available.
Looking at the guidelines and crossover topics, the reservations document handles group bookings and how large groups are managed, including policies like minimum spends and cancellation. The question about customized packages likely relates to reservation policies, which are covered in the reservations document.
The upcoming events document includes info on public events, weekly/monthly happenings, and special one-off events. However, private gatherings or group bookings aren't part of that document. Since the query is about organizing a private event or group booking, it's under the reservations document's purview. Therefore, the upcoming events document isn't relevant here and should be excluded.
</think>
{
"reasoning": "The query asks about customized packages for group bookings or private gatherings. This relates to reservation policies, group handling, and private event logistics, which are covered in the reservations document. The upcoming events document only contains information about public events, weekly/monthly activities, or special one-off experiences. Since private gatherings and group booking packages fall under reservations and venue policies, the upcoming events document is not relevant to answering this query.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I book a private event or group gathering with a meal 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.
<｜Assistant｜>
<think>
Okay, let's tackle this query: "Can I book a private event or group gathering with a meal package deal?"
First, I need to determine if the upcoming events document is relevant here. The user is asking about booking a private event or group gathering with a meal package. From the guidelines, private events and group bookings are handled by the reservations document, not the upcoming events. The upcoming events document is for public events like special occasions, weekly/monthly happenings, not private bookings.
Looking at the crossover topics, group bookings and private events fall under the reservations document. The upcoming events doc doesn't cover space rentals or private events. The query is about arranging a private event, which involves reservations policies, group handling, and possibly meal packages, which are in the reservations and menu docs. Since the user's query is about booking, which is a reservation matter, the upcoming events document isn't needed here.
So, the decision should be to exclude the upcoming events document because the query is addressed by the reservations and possibly menu documents, not the events info.
</think>
{
"reasoning": "The query asks about booking a private event or group gathering with a meal package deal. This type of inquiry pertains to reservations, group policies, and meal packages, which are covered by the reservations and menu documents. The upcoming events document does not contain information about private bookings, group reservations, or meal deals, as it focuses on public events like one-off special occasions, weekly/monthly events, and event-specific rules. Since the query is about reserving a space and meal packages rather than attending or inquiring about an event, the upcoming events document is not relevant.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you offer package deals for group bookings or private events with entertainment?
### 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.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking about package deals for group bookings or private events with entertainment.
First, I need to check what's covered in the upcoming events document. From the prompt, that document includes special one-off events, weekly/monthly events, their dates, tickets, and policies related to those events. It doesn't mention anything about private events or group bookings.
The query is specifically about package deals for groups or private events. Looking at the crossover topics, group bookings and private events are handled by the reservations document. The reservations document includes info on group handling, minimum spends, and how to make reservations for such events. The package deals might involve pricing and amenities, which could also be in the venue information document regarding facilities and charges.
Since the upcoming events document only covers public events and their details, and the user's question is about organizing a private event or group booking, the relevant info would be in reservations or venue info documents. Therefore, the upcoming events document isn't needed here and should be excluded.
</think>
{
"reasoning": "The query asks about package deals for group bookings or private events with entertainment. The upcoming events document does not handle private events or group bookings, as these are covered by the reservations document. Additionally, package deals and entertainment arrangements fall under venue policies and reservation details rather than public events listed in the upcoming events document. Therefore, the upcoming events document is not relevant to this query.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I reserve a private event or group gathering with a tailored 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.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking about reserving a private event or group gathering with a tailored package deal. The key here is to figure out which document handles this kind of query.
Looking at the crossover topics, the reservations document includes info on how groups and large bookings are handled, minimum spends for reserved areas, and details on making reservations. The query is specifically about private events and tailored packages, which falls under group bookings.
The upcoming events document, on the other hand, lists public events like live music or themed nights, not private bookings. Since the user isn't asking about attending an event but rather organizing their own private one, the reservations document is the relevant one here. Therefore, the upcoming events document doesn't contain the needed information, so it should be excluded.
</think>
{
"reasoning": "The query is about reserving a private event or group gathering with a tailored package deal. This falls under group booking policies and reservation-specific details, which are covered in the reservations document. The upcoming events document focuses on public events, special one-off experiences, or weekly/monthly activities open to all patrons. Since private group reservations and tailored packages are not part of the events document's scope, it should be excluded from the context for this query.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you offer any unique packages for private events or group gatherings?
### 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.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking if there are any unique packages for private events or group gatherings. The key here is to determine which document would handle this query.
The upcoming events document contains info on one-off or recurring public events like live music, comedy nights, or special occasions. However, private events and group bookings are specifically mentioned in the guidelines as being handled by the reservations document. The reservations doc includes details on group handling, seating layouts, and reservation policies. Since the query is about private packages and group gatherings, it falls under the reservations document's responsibility. The upcoming events document doesn't cover private bookings, so including it here wouldn't help. Therefore, the answer lies in the reservations document, not the events one. So, exclude the upcoming events document.
</think>
{
"reasoning": "The query asks about unique packages for private events or group gatherings. The reservations document handles group bookings, private events, and details on reservation policies, including packages and minimum spends. The upcoming events document specifically covers public events like live music, comedy nights, or seasonal activities, not private event packages. Since the query pertains to services managed by the reservations document, the upcoming events document is not relevant here.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any themed 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.
<｜Assistant｜>
<think>
Okay, I need to determine whether the upcoming events document is relevant for answering the user's query about themed packages for group bookings or private events. Let me break this down.
First, the query is specifically asking about themed packages for group bookings or private events. From the provided guidelines, I remember that private events and group bookings are handled by the reservations document, not the upcoming events document. The upcoming events document covers public events like special one-offs, weekly, or monthly events.
Looking at the crossover topics, the reservations document includes information on how groups and large bookings are handled. Themed packages for private events would fall under the reservations document's details about group policies, minimum spends, and how such bookings are managed. The upcoming events document doesn't mention handling private events or group packages; it's more about public events that anyone can attend.
Additionally, the guidelines state that if the query is about booking a table for an event or private events, it's the reservations document's responsibility. Since the user is asking about themed packages for groups or private events, this directly relates to the reservations document's content. Therefore, including the upcoming events document here isn't necessary because the answer lies elsewhere.
Therefore, the decision should be to exclude the upcoming events document from the context.
</think>
{
"reasoning": "The query asks about themed packages for group bookings or private events, which are related to reservations and group policies. The upcoming events document does not handle private events or group booking packages, as these are covered by the reservations document. The contents of the upcoming events document (special, weekly, or monthly public events) are unrelated to private group bookings or themed packages for reserved spaces.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I book a group event or private gathering with a meal and entertainment 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.
<｜Assistant｜>
<think>
Alright, let me work through this step by step. The user is asking about booking a group event or private gathering with a meal and entertainment package. I need to determine if the upcoming events document is relevant here.
First, looking at the contents of the upcoming events document: it covers special one-off events, weekly/monthly events, their dates, times, ticket info, and policies. It's for public events like anniversaries, holidays, live music, etc.
The query is about booking a group or private event. According to the guidelines, private events and space rentals are handled by the reservations document, not the upcoming events. The upcoming events document only lists public events. Since the user is asking about a private gathering, the reservations document would have the necessary info on group bookings, minimum spends, and how to make reservations.
Additionally, the crossover topics mention that group bookings and reservation policies are covered in the reservations document. Even though the query mentions an entertainment package, unless it's part of a public event listed in the upcoming events, it's still a reservation matter. Therefore, the upcoming events document isn't needed here.
</think>
{
"reasoning": "The query is about booking a group event or private gathering with a meal and entertainment package. This type of request relates to reservations, group policies, and service packages, which are handled by the reservations document. The upcoming events document specifically covers public events like live music, workshops, or seasonal celebrations, not private group bookings. Since the core of the query falls under reservation policies and group handling, the upcoming events document is not relevant for addressing the user's needs.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you have package options for group bookings or private gatherings with additional services?
### 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.
<｜Assistant｜>
<think>
Okay, let me try to figure this out. The user is asking about package options for group bookings or private gatherings with additional services.
First, I need to see which documents handle group bookings. The query mentions packages for groups and private events, which sounds like it's about reservations and possibly special services. Checking the crossover topics, the Reservations document handles group bookings, private gatherings, and details on how they manage large groups, including package options. The Venue Information document might have details on facilities and amenities that could be part of a package, but the actual package options and policies would be in Reservations.
The Upcoming Events document mainly covers public events like special nights, workshops, or holidays. Since the user is asking about private group bookings and packages, that's not covered in events. Events are for public happenings, not private reservations. The question isn't about attending an event but organizing their own private gathering. Therefore, the Reservations and maybe Venue Information documents are relevant here, not the Upcoming Events. So the correct decision is to exclude the Upcoming Events document.
</think>
{
"reasoning": "The query asks about package options for group bookings or private gatherings with additional services. This type of inquiry pertains to reservation policies, group handling, and venue facilities for private events, which are covered by the Reservations and Venue Information documents. The Upcoming Events document does not contain information about private bookings, packages, or venue-specific policies for group reservations. Instead, it focuses on public events, special occasions, or recurring weekly/monthly activities. Since the query is unrelated to event details and is instead about group booking logistics, the Upcoming Events document is not relevant.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any special event 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.
<｜Assistant｜>
<think>
Okay, let me try to figure out whether the upcoming events document should be included for the query "Are there any special event packages for private events or group bookings?"
First, I need to check what's in the upcoming events document. From the prompt, the upcoming events document covers special one-off events, weekly events, and monthly events that are open to the public. These include things like tastings, live music, comedy nights, or special occasions like New Year's Eve. It also includes details about dates, times, tickets, and policies specific to those events.
Now, the user is asking about special event packages for private events or group bookings. Private events and group bookings usually involve reserving a space in the venue for a specific group, which isn't open to the public. The reservations document handles information about group bookings, policies, minimum spends, how to make reservations, etc. The guidelines mention that private events and space rentals are covered by the reservations document, not the events document.
The upcoming events document is only for public events. Since the query is about packages for private events, the relevant information would be in the reservations document, not the events one. Even if the user mentioned "special event packages," if those packages are for private bookings, they're handled by reservations. There's no mention of private event packages in the upcoming events document contents.
So, according to the guidelines, any query about group bookings or private events should be directed to the reservations document. Therefore, the upcoming events document isn't needed here. The decision should be to exclude it.
</think>
{
"reasoning": "The query asks about special event packages for private events or group bookings. The upcoming events document only contains information about public events such as one-off, weekly, or monthly events open to the general public. Private event packages and group booking policies are handled exclusively by the reservations document, which covers reservation policies, group handling, and private event logistics. Since the query pertains to private or group-specific arrangements, the upcoming events document is not relevant here.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I arrange a group event or private gathering with a discounted 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.
<｜Assistant｜>
<think>
Alright, let's break this down. The user is asking about arranging a group event or private gathering with a discounted package. First, I need to determine which document handles this kind of query. The upcoming events document includes special one-off or recurring events like comedy nights or New Year's parties, but private gatherings or group bookings would fall under reservations. The reservations document specifically covers group bookings, minimum spends, and how large groups are handled. Since the query is about organizing a private event and possible discounts, it's more about booking policies and packages, which are in the reservations document. The upcoming events document doesn't deal with private bookings, so it should be excluded.
</think>
{
"reasoning": "The query asks about arranging group events or private gatherings with discounted packages. This falls under group booking policies and reservation packages, which are covered in the reservations document. The upcoming events document does not contain information about private event logistics, discounts, or group booking policies, as it focuses on public events like live music or workshops. Therefore, the upcoming events document is not relevant to this query.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you have any group event or private booking packages with added perks?
### 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.
<｜Assistant｜>
<think>
Alright, let's break this down. The user is asking about group events or private booking packages with added perks. The task is to decide if the upcoming events document is relevant here.
First, looking at the contents of the upcoming events document: it covers one-off events, weekly and monthly events like special occasions, workshops, live music, etc. It's about public events, not private bookings.
Now, the query is specifically about group event packages and private bookings. According to the guidelines, private events and space rentals are handled by the reservations document, not the upcoming events one. The reservations document includes info on how groups and large bookings are managed, policies, minimum spends, etc. That's where the answer would be found, not in the events document which is for public events.
Also, the crossover topics mention that group bookings are the domain of the reservations document. So even though the user mentioned "group event," it's about booking packages, which doesn't fall under the upcoming events. Therefore, the upcoming events document doesn't have the necessary info here. The decision should be to exclude it.
</think>
{
"reasoning": "The query asks about group event or private booking packages with added perks. According to the guidelines, private events and space rentals are handled by the reservations document, not the upcoming events document. The upcoming events document focuses on public events (e.g., live music, workshops) and does not include details about group booking policies, packages, or perks. Since this query pertains to reservations and group booking logistics, the reservations document is the relevant context, making the upcoming events document unnecessary for addressing the request.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I book a group event or private gathering with a comprehensive event 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.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking about booking a group event or private gathering with a comprehensive event package. First, I need to determine if the upcoming events document is relevant here.
Looking at the contents of the upcoming events document, it includes special one-off events, weekly events, and monthly events, along with their details like dates, tickets, and descriptions. However, the query here is about booking a private group event, which isn't something listed in the upcoming events. Those are public events.
Next, the crossover topics mention that reservations and venue information handle group bookings. The reservations document specifically covers how groups and large bookings are handled, including policies and reservation procedures. The venue information document includes details about the venue's capacity and facilities, which are necessary for planning a private event. The query is about the logistics of booking and event packages, which are handled by these other documents.
Since the upcoming events document only lists public events and doesn't deal with private bookings or packages, the correct decision is to exclude it. The answer will rely on the reservations and venue information documents instead.
</think>
{
"reasoning": "The query asks about booking a group event or private gathering with a comprehensive event package. This pertains to reservations, group policies, and venue capacity/facilities, which are covered in the reservations and venue information documents. The upcoming events document only contains information about public events (e.g., live music, workshops) and does not handle private event bookings or packages. Therefore, the upcoming events document is not relevant to this query.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any special offers or packages for hosting group 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.
<｜Assistant｜>
<think>
Alright, let's analyze the query: "Are there any special offers or packages for hosting group or private events?"
First, the user is asking about special offers or packages specifically for group or private events. The key terms here are "special offers," "packages," and "hosting group or private events."
Looking at the Crossover Topics, the Reservations Document includes information on how groups and large bookings are handled, policies like minimum spends, time limits, and cancellation policies. It also covers service charges and handling group reservations. The Venue Information Document might have details on capacity and facilities, but the query is specifically about offers and packages, which likely fall under the Reservations Document's scope.
The Upcoming Events Document, as outlined, focuses on public events like special one-offs, weekly, or monthly events, including details like dates, tickets, and descriptions. Hosting private group events isn't listed here. Instead, private events and group bookings are explicitly mentioned under the Reservations Document's responsibilities.
Additionally, the Guidelines state that private events and space rentals are handled by the Reservations Document, not the Upcoming Events Document. Since the query is about offers for hosting such events, the relevant information would be in the Reservations Document. Therefore, the Upcoming Events Document isn't needed here and should be excluded.
</think>
{
"reasoning": "The query asks about special offers or packages for hosting group or private events. The Reservations Document explicitly handles group bookings, policies, and service charges, while the Upcoming Events Document focuses on public events (e.g., live music, workshops) rather than private event hosting. Since private/group event logistics and offers are managed by the Reservations Document, the Upcoming Events Document is not relevant to this query.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you offer packages for group bookings or private events with full service?
### 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.
<｜Assistant｜>
<think>
Okay, let's break down this query. The user is asking if the venue offers packages for group bookings or private events with full service.
First, I need to check what each document covers. The upcoming events document has info on one-off, weekly, and monthly events like special occasions, live music, etc. It's about events open to the public that people can attend, not private bookings.
The reservations document handles group bookings, private events, and reservations policies. The user's query is specifically about group bookings and private events, which according to the guidelines, are handled by the reservations document. The upcoming events document doesn't cover private events or space rentals—those are in the reservations doc.
Since the question is about organizing a private event or group package, the answer would be found in the reservations document, not the upcoming events. Therefore, including the events document here isn't necessary. The decision should be to exclude the upcoming events document from the context.
</think>
{
"reasoning": "The query asks about group booking packages and private events with full service. These topics fall under reservations and venue policies, which are covered in the Reservations Document and Venue Information Document. The Upcoming Events Document only contains details about public events (e.g., live music, workshops, or seasonal celebrations) and does not address private event packages, group booking policies, or service charges. Since the query relates to organizing private events or group reservations, the relevant information would be sourced from the Reservations Document, not the Upcoming Events Document.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I arrange a private event or group gathering with an all-inclusive 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.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking about arranging a private event or group gathering with an all-inclusive package. Now, I need to check if the upcoming events document is relevant here.
First, the upcoming events document covers special one-off events, weekly/monthly events, things like live music, comedy nights, workshops, etc. These are public events. The query is about private events, which the guidelines say are handled by the reservations document, not the events document.
Also, all-inclusive packages would likely involve booking private space, which falls under group bookings. The reservations document includes info on how groups and large bookings are handled, including policies on minimum spends, seating, etc. The venue info document might also be involved for space details, but the events document isn't needed here.
Since private events and group bookings are explicitly mentioned as handled by the reservations document, the upcoming events document isn't relevant. The user isn't asking about attending a public event but organizing their own. Therefore, exclude the upcoming events document.
</think>
{
"reasoning": "The query is about arranging a private event or group gathering with an all-inclusive package. 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 special occasions, workshops, or recurring weekly/monthly activities. Since the user is inquiring about organizing their own private event rather than attending a publicly listed one, the upcoming events document does not contain relevant information for this request.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any package options 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.
<｜Assistant｜>
<think>
Okay, let's tackle this query. The user is asking about package options for private or group bookings. First, I need to determine which document handles this. The upcoming events document covers one-off events, weekly/monthly happenings, but private bookings would be under reservations. The crossover topics mention that group bookings and reservations are handled by the reservations document. The query is about packages for those bookings, so it's more about policies, pricing, and options, which the reservations doc includes. The upcoming events doc doesn't cover private event packages. Therefore, exclude the events document.
</think>
{
"reasoning": "The query specifically asks about package options for private or group bookings, which falls under the reservations document. The upcoming events document does not contain information on booking packages, private events, or group reservation policies. Since the reservations document handles all details regarding group bookings, minimum spends, and reservation policies, the upcoming events document is irrelevant to this query.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I book a group event or private gathering with a premium 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.
<｜Assistant｜>
<think>
Okay, let's analyze the query: "Can I book a group event or private gathering with a premium package?"
First, the user is asking about booking a group event or private gathering. The premium package part might relate to special services or amenities offered for such events.
Looking at the upcoming events document contents, it covers special one-off events, weekly/monthly events, and their details like dates, tickets, and descriptions. However, queries about booking group events or private gatherings fall under the reservations document. The reservations document handles how groups and large bookings are managed, including policies, minimum spends, and reservation procedures.
The guidelines mention that private events and space rentals are handled by the reservations document, not the upcoming events. Since the user is asking about booking a group event (which is a private gathering), this is definitely under the reservations document's responsibility. The upcoming events document is for public events, not private bookings.
Therefore, the upcoming events document doesn't contain information relevant to this query. The decision should be to exclude it.
</think>
{
"reasoning": "The query is about booking a group event or private gathering with a premium package. This relates to reservations, group policies, and package details, which are covered in the reservations document. The upcoming events document does not handle private bookings or group reservations, as it only includes public events, weekly/monthly activities, or one-off experiences. Therefore, the upcoming events document is irrelevant to the query and should be excluded.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you provide event packages for hosting private events or group gatherings?
### 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.
<｜Assistant｜>
<think>
Okay, let's start by understanding the query. The user is asking, "Do you provide event packages for hosting private events or group gatherings?" They want to know if the venue offers packages for hosting their own private events or group gatherings.
Now, looking at the Upcoming Events document contents. That document covers special one-off events, weekly events, and monthly events that the venue itself is hosting. These are events open to the public, like live music, comedy nights, or holiday celebrations. It also includes details about tickets, dates, and descriptions of these events. The key point here is that these are events organized by the venue for public attendance.
The query, however, is about private events or group gatherings that the user might host. That falls under reservations and venue information. The Reservations document handles group bookings, policies, minimum spends, and how to reserve spaces. The Venue Information document includes details about capacity, facilities, and amenities which are relevant for hosting private events.
The guidelines mention that private events and space rentals are handled by the Reservations document, not the Upcoming Events. Since the user is asking about packages for hosting their own events, this is related to reservations and venue capacity, not the venue's public events listed in Upcoming Events. Therefore, the Upcoming Events document isn't needed here. The correct context would come from the Reservations and Venue Information documents instead.
</think>
{
"reasoning": "The query asks about event packages for private events or group gatherings. The upcoming events document contains information about public events hosted by the venue (e.g., live music, workshops, seasonal celebrations), not private event hosting. Private event packages, group reservations, and venue capacity details fall under the reservations and venue information documents, which handle policies, facilities, and booking procedures for such requests. The upcoming events document does not cover private event hosting or group reservation packages.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any package deals available 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.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking about package deals for private events or group bookings. 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 holiday celebrations. Private events and group bookings aren't part of that—those are handled by the reservations document.
The query specifically mentions "private events" and "group bookings," which according to the guidelines, are under the reservations document's purview. Package deals for these would involve reservation policies, minimum spends, and how groups are handled, all covered in reservations.
The upcoming events document doesn't deal with private bookings or group packages. So 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 is about package deals for private events or group bookings, which falls under the reservations document's responsibility. The upcoming events document only covers public events like special occasions, weekly/monthly happenings, and does not handle private bookings or group reservation packages. Therefore, the upcoming events document is not relevant here.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you offer packages for hosting a group event or private gathering with VIP service?
### 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.
<｜Assistant｜>
<think>
Okay, let's take a look at the user's query: "Do you offer packages for hosting a group event or private gathering with VIP service?" The user is asking about packages for private group events or gatherings with VIP services.
First, I need to determine which document would contain the relevant information. The upcoming events document includes special one-off events, weekly or monthly events, and their details. However, the query here is about hosting a private event, which isn't an event organized by the venue for the public. Instead, this is about a customer wanting to book the venue for their own private event.
Looking at the crossover topics, group bookings and private gatherings are handled by the reservations document, as per the guidelines. The reservations document covers policies for group bookings, minimum spends, reservation procedures, and how large groups are handled. VIP services might relate to special packages, which would also be part of the reservation policies or venue information regarding services and charges.
The upcoming events document doesn't include private events or space rentals; those are in the reservations document. Therefore, even though the query is about events, it's specifically about private ones, so the upcoming events document isn't relevant here. The correct documents to include would be the reservations and venue information documents. Hence, the upcoming events document should be excluded.
</think>
{
"reasoning": "The query asks about packages for hosting group events or private gatherings with VIP service. This relates to group bookings, private event policies, and service charges, which are covered in the reservations and venue information documents. The upcoming events document does not contain information about private event packages, as it focuses on public events (e.g., live music, workshops) and venue-organized activities. Therefore, the upcoming events document is not relevant here and should be excluded.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I book a private event or group gathering with a complete event 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.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking about booking a private event or group gathering with a complete event package. First, I need to check what each document covers. The upcoming events document includes special one-offs, weekly, or monthly events that are open to the public, like live music or workshops. But the query here is about private bookings and event packages.
Looking at the crossover topics, the reservations document handles group bookings, reservation policies, and private events. The venue information document covers facilities and amenities which might be relevant for event spaces. Since the user is specifically asking about booking a private event, this falls under the reservations document's responsibility, not the upcoming events. The upcoming events doc doesn't deal with private bookings, only public events. So the correct decision is to exclude the upcoming events document here.
</think>
{
"reasoning": "The query asks about booking a private event or group gathering with an event package. The upcoming events document does not cover private event bookings or group reservations, as these are explicitly handled by the reservations document. The events document only includes public events, special one-offs, weekly/monthly activities, and event-specific policies, none of which pertain to private bookings. Therefore, the upcoming events document is irrelevant for this query.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you offer packages for private events or group bookings with special pricing?
### 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.
<｜Assistant｜>
<think>
Okay, let me break this down. The user is asking if the venue offers packages for private events or group bookings with special pricing. I need to figure out if the upcoming events document is relevant here.
First, looking at the query, it's about private events and group bookings. Now, according to the guidelines, private events and group bookings are handled by the reservations document, not the upcoming events document. The upcoming events document covers public events like special one-offs, weekly, or monthly events.
The reservation document's contents include how groups and large bookings are handled, policies on minimum spends, cancellation, and information on seating layouts for group sizes. The query specifically mentions packages and special pricing for these group bookings, which would be part of the reservation policies.
The upcoming events document doesn't deal with private events or group booking packages. Since the user isn't asking about public events, special occasions, or event details like dates and times, there's no need to include the events document. The answer can be fully addressed by the reservations document, so excluding the upcoming events document is the right call.
</think>
{
"reasoning": "The query asks about private event packages and group booking pricing, which pertains to reservation policies and special pricing arrangements. The upcoming events document does not handle private events or group bookings; these are covered by the reservations document. Since the query focuses on logistics for private events (e.g., pricing, packages) rather than public events listed in the upcoming events document, excluding this document aligns with the guidelines.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I arrange a group event or private gathering with a luxury 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.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking about arranging a group event or private gathering with a luxury package. I need to determine if the upcoming events document is relevant here.
First, the upcoming events document covers special one-off events, weekly/monthly happenings, things like live music, comedy nights, etc. It's about public events that anyone can attend. The query isn't about attending an existing event but organizing a private group event.
Looking at the crossover topics, the reservations document handles group bookings, private events, and reservation policies. The venue information might have details on capacity and facilities, but the user specifically mentions a luxury package, which might involve reservations and private arrangements, not public events.
The guidelines say private events and space rentals are handled by the reservations document, not the upcoming events. Since this query is about organizing a private gathering, the upcoming events doc isn't needed. So the decision is to exclude.
</think>
{
"reasoning": "The user's query is about arranging a group event or private gathering with a luxury package. This type of request pertains to reservations, group booking policies, and venue facilities for private functions, all of which are covered by the **reservations document** and **venue information document**. The **upcoming events document** does not include information about private event coordination, space rentals, or group-specific packages, as it focuses on publicly accessible events (e.g., live music, workshops, holiday celebrations). Since the query falls under the scope of reservations and venue logistics rather than public event details, the upcoming events document is irrelevant here.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any event package options 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.
<｜Assistant｜>
<think>
Okay, let's tackle this query. The user is asking about event package options for group bookings or private events. 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 holiday celebrations. Private events and group bookings, however, are handled by the reservations document according to the guidelines. The query specifically mentions group bookings and private events, which are the responsibility of the reservations team. The upcoming events document doesn't cover private event packages, so including it wouldn't help here. Therefore, the decision is to exclude the upcoming events document.
</think>
{
"reasoning": "The query asks about event package options for group bookings or private events. According to the guidelines, private events and group bookings are handled by the reservations document, not the upcoming events document. The upcoming events document only contains information about public events (special one-offs, weekly/monthly events) and does not cover private event packages or group reservation policies. Therefore, the upcoming events document is not relevant for this query.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I reserve a special package 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.
<｜Assistant｜>
<think>
Okay, let's look at the query: "Can I reserve a special package for group bookings or private events?" The user is asking about reserving a special package for groups or private events.
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, tickets, and policies. But group bookings and private events are mentioned in the reservations document. The guidelines say that private events and space rentals are handled by reservations, not the events document.
The query is about reserving packages, which relates to reservation policies and how the venue handles group bookings. Since the reservations document covers group bookings and private events, the upcoming events document isn't needed here. Even though the user mentions a "special package," that's about the reservation process, not public events. Therefore, exclude the upcoming events document.
</think>
{
"reasoning": "The query asks about reserving special packages for group bookings or private events. The reservations document specifically handles group bookings, private events, and reservation policies, including details on packages and how such events are managed. The upcoming events document contains information about public events, workshops, and special occasions but does not cover reservations or private event packages. Therefore, the upcoming events document is not relevant to answering this query.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you offer group booking packages that include food and drinks for 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.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking about group booking packages that include food and drinks for private events.
First, I need to check if this query relates to the contents of the upcoming events document. That document covers special one-off events, weekly/monthly events, and details like dates, tickets, and event descriptions. Private events or space rentals aren't part of it—those are handled by the reservations document.
The query is specifically about group bookings for private events, which involves reservation policies, packages, and possibly minimum spends or how groups are handled. All of these are covered in the reservations document according to the crossover topics. The upcoming events document doesn't deal with private bookings or packages, so including it wouldn't help answer the user's question. Therefore, the decision should be to exclude the upcoming events document here.
</think>
{
"reasoning": "The query asks about group booking packages for private events, which involves reservation policies, package inclusions, and handling of large groups. These topics are covered in the reservations document, specifically detailing group bookings, minimum spends, and venue policies. The upcoming events document does not contain information about private event bookings, venue policies for group reservations, or food/drink packages, as these fall under the reservations and menu documents. Since the query pertains to private event logistics rather than public events or event schedules, the upcoming events document is not relevant.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there private event packages with options for group bookings 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.
<｜Assistant｜>
<think>
Okay, let me see. The user is asking about private event packages and group booking options. First, I need to check where this kind of information would be located.
The query mentions "private event packages" and "group bookings." From the provided guidelines, the reservations document handles group bookings and private events. The upcoming events document is for public events like live music or special occasions, not private packages.
The crossover topics list says reservations handle group booking policies, packages, and how to make reservations. The upcoming events document doesn't cover private events. Since the user's question is about private packages and group bookings, the answer would be in the reservations document, not the upcoming events.
So, the upcoming events document isn't relevant here. Therefore, I should exclude it.
</think>
{
"reasoning": "The query asks about private event packages and group booking options, which fall under reservations and venue policies. The upcoming events document does not contain information on private event packages or group booking policies, as those are covered in the reservations document. Since the query pertains to group bookings and private event logistics—not public events listed in the upcoming events document—it should be excluded from the context.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you offer all-inclusive packages for private events or group gatherings?
### 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.
<｜Assistant｜>
<think>
Okay, let me analyze this query. The user is asking about all-inclusive packages for private events or group gatherings. First, I need to check what each document covers. The upcoming events document includes special one-off events, weekly/monthly events, and their details. But the query here is about private events and group packages, which are handled by the reservations document. The reservations document covers group bookings, reservation policies, minimum spends, etc. Since the user's question is about packages for private groups, it's related to reservations and venue information, not public events listed in the upcoming events. Therefore, the upcoming events document isn't needed here. The answer should be to exclude it.
</think>
{
"reasoning": "The query is about all-inclusive packages for private events or group gatherings. This type of inquiry relates to reservation policies, group booking handling, and venue facilities for private functions, which are covered in the reservations and venue information documents. The upcoming events document specifically deals with public events like special occasions, workshops, or recurring weekly/monthly activities open to the general public. Since private event packages and group gatherings fall under reservation and venue policies rather than public event listings, the upcoming events document is not relevant to answering this query.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I get a package for group bookings or private events with room rentals?
### 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.
<｜Assistant｜>
<think>
Okay, let me break down the user's query to see if the upcoming events document is needed. The user is asking about group booking packages or private events with room rentals.
First, looking at the upcoming events document contents: it covers one-off and recurring events like special occasions, workshops, or live music. These are public events. The reservations document, however, handles group bookings, private events, and room rentals.
The query specifically mentions group bookings and private events, which fall under the reservations document according to the crossover topics. Since the upcoming events document doesn't include private or group booking info but instead lists public events, it's not relevant here. The answer should come from the reservations document, so the upcoming events document should be excluded.
</think>
{
"reasoning": "The query is about group bookings and private event packages with room rentals. These topics are related to reservation policies and venue facilities, which are covered in the reservations and venue information documents. The upcoming events document specifically addresses public events (e.g., live music, workshops) and does not include details about private event packages, group reservations, or venue rental policies. Since the query pertains to bookings and private events, the reservations document is the appropriate context.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you offer any exclusive event 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.
<｜Assistant｜>
<think>
Okay, so the user is asking if the venue offers exclusive event packages for private events or group bookings. Let me check the guidelines. The upcoming events document includes special one-off events, weekly, and monthly events that are open to the public. Private events and group bookings, though, are handled by the reservations document. The query here is about private events and group packages, which isn't covered in the upcoming events. Instead, the reservations document would have info on how groups and large bookings are managed. Therefore, the upcoming events document isn't relevant here. So the decision should be to exclude.
</think>
{
"reasoning": "The query is about exclusive event packages for private events or group bookings. The upcoming events document does not handle private events or group bookings, as these are managed by the reservations document. The upcoming events document only covers public events such as special one-off, weekly, or monthly events. Since the query pertains to private group bookings and event packages, the reservations document is the appropriate context, making the upcoming events document irrelevant for this specific inquiry.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I arrange a group event or private function with a discounted 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.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking about arranging a group event or private function with a discounted package deal. First, I need to check what each document covers.
The upcoming events document includes one-off events, weekly/monthly happenings, and details like dates and tickets. Group bookings and private functions, though, are handled by the reservations document according to the guidelines. The query here is specifically about group events and discounts, which falls under how the venue handles reservations and packages. The venue information doc might have capacity and facilities, but the actual arrangements, packages, and discounts are in reservations. Since the upcoming events don't cover private bookings or group deals, the decision is to exclude the events doc here.
</think>
{
"reasoning": "The query is about arranging a group event or private function with a discounted package deal. This falls under the reservations document, which handles group bookings, private functions, and policies related to reservations. The upcoming events document only covers public events like live music, workshops, or seasonal celebrations, not private bookings or group package deals. Since the core of the query relates to reservations and group policies, the upcoming events document is irrelevant here.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any packages for booking private events or group functions 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.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking about packages for booking private events or group functions. The upcoming events document, as described, contains info on special one-off events, weekly, and monthly events that are open to the public. Private events and group bookings, like what the user is asking about, would involve things like reservation policies, minimum spends, and how the venue handles large groups. According to the crossover topics, these are covered in the reservations document, not the upcoming events document. The guidelines also state that private events and space rentals are handled by reservations. Since the query is about group bookings and private events, the upcoming events doc isn't relevant here. So, the decision should be to exclude.
</think>
{
"reasoning": "The query asks about packages for booking private events or group functions, which relates to policies, reservations, and handling of group bookings. The upcoming events document does not cover private events or group bookings, as these are explicitly handled by the reservations document. The reservations document contains information on group policies, minimum spends, and how such bookings are managed, making the upcoming events document irrelevant for this query.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you offer any event packages for private events or group reservations with added services?
### 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.
<｜Assistant｜>
<think>
Alright, let's tackle this query. The user is asking if the venue offers event packages for private events or group reservations with added services.
First, I need to check what's covered in the Upcoming Events document. From the prompt, that document includes special one-off events, weekly or monthly events, things like live music, comedy nights, or holiday celebrations. It also has details like dates, times, tickets, and event policies. But private events or group bookings aren't part of this document.
Looking at the crossover topics, the Reservations document handles group bookings, private events, and reservation policies. The query specifically mentions "private events" and "group reservations," which fall under the Reservations document's responsibilities. The added services might relate to packages, which would involve reservation policies, minimum spends, or facility use—all covered there.
The guidelines mention that private events and space rentals are handled by the Reservations document, not Upcoming Events. Since the user isn't asking about public events but rather private packages, the Upcoming Events document isn't relevant here. The decision should be to exclude it because the answer lies in the Reservations document.
</think>
{
"reasoning": "The query asks about event packages for private events or group reservations with added services. These topics pertain to reservation policies, group handling, and service packages, which are covered under the reservations document. The upcoming events document does not contain information on private bookings or group reservation packages, as it focuses on public events like one-off or recurring activities. Therefore, the upcoming events document is not relevant here.",
"decision": "exclude"
}
<｜end▁of▁sentence｜>
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.