text stringlengths 7.09k 9.53k |
|---|
<｜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 reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any events I need to book in advance?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's see. The user is asking, "Are there any events I need to book in advance?" The task is to decide if the reservations document should be included.
First, I need to check the query's main focus. The user is asking about events that require advance booking. The events themselves are covered in the upcoming events document, which lists details like dates, times, and whether tickets are needed. But the key here is "need to book in advance."
The reservations document includes info on policies about reservations, including whether certain events require them. Even though the events are in another document, the part about needing a reservation or booking would relate to the reservation policies. For example, the reservations document might mention if certain events have different booking requirements or if there's a minimum spend for reserved areas during events.
Also, the guidelines mention that if the query asks whether a reservation is required, the reservations document must be included. Even if the main event details are elsewhere, knowing if booking is needed ties into reservation policies. The next node might need the reservations doc to confirm if events have specific reservation rules, even if the event info is in another document. Therefore, including it provides necessary context about booking requirements.
</think>
{
"reasoning": "The query asks about events that require advance booking. While event details are in the 'upcoming events document', the need to 'book in advance' directly relates to reservation policies and procedures. The reservations document contains information on reservation requirements, cancellation policies, and how bookings are handled for events (e.g., minimum spends, time limits). Including it ensures the next node can verify if reservations are mandatory for specific events and provide context about booking processes, even though event descriptions are in a separate document.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do I need to make a reservation for any upcoming events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's analyze this query: "Do I need to make a reservation for any upcoming events?"
First, the user is asking about the necessity of reservations for upcoming events. The core of the query is whether a reservation is required. The upcoming events document would handle details about the events themselves, like dates and descriptions. However, the part about needing a reservation directly relates to reservation policies.
Looking at the reservations document contents, it includes policies like whether reservations are needed, especially for events. The guidelines state that if the query involves whether a reservation is required, even if it's for an event, the reservations document must be included. Even though the events are covered in another document, the necessity of booking falls under reservation policies. The next node would need the reservations document to confirm if reservations are mandatory for events, even if event details come from elsewhere. So, include the reservations document here.
</think>
{
"reasoning": "The query asks whether reservations are needed for upcoming events. While event details are covered in the Upcoming Events document, the need for reservations directly relates to reservation policies and requirements. The reservations document contains information on reservation necessity for different scenarios, including events. Including it allows the next node to verify reservation requirements even when event-specific policies might exist.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any ticketed events I should book?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "Are there any ticketed events I should book?" The main focus here is on ticketed events. Now, according to the crossover topics, information about events, including whether they need tickets, is covered in the Upcoming Events Document. That document includes details like event dates, times, ticket requirements, and event descriptions.
However, the guidelines mention that if the query involves whether a reservation is needed or any booking intent, the reservations document should be included. The user used the word "book," which implies an action related to making a reservation or booking. Even though the primary information about ticketed events is in the Upcoming Events Document, the mention of "book" suggests that the next node might need to check if reservations are required for these events, which would involve the reservations document.
Additionally, the reservations document includes policies on how to make reservations and handle large groups, which might be relevant if booking a ticketed event requires specific reservation steps. So even though the ticketed events are covered elsewhere, the act of booking could require context from the reservations document. Therefore, including it ensures the next node has all necessary context to address any reservation-related aspects of booking the event.
</think>
{
"reasoning": "The query asks about ticketed events and uses the term 'book', which signals intent related to reservations or booking actions. While event details (including ticketed status) are covered in the Upcoming Events Document, the mention of 'book' implies the next node may need to reference reservation policies (e.g., whether reservations are required for events, how to secure tickets via booking). The reservations document provides critical context for reservation procedures and policies that may apply to event bookings, even if the core event details reside elsewhere.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you have any events that require booking?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "Do you have any events that require booking?" The first thing I need to consider is which document contains the information about events. According to the crossover topics, the Upcoming Events Document includes details about special events, weekly or monthly events, and whether a ticket is needed. That makes me think the main answer would come from there.
But wait, the question is specifically about events that "require booking." Even though the events themselves are in the Upcoming Events Document, the requirement for booking might relate to the reservation policies. The Reservations Document includes policies on reservations, including how groups and large bookings are handled. If an event requires a reservation, that policy would be in the Reservations Document.
Also, the guidelines mention that if the query asks whether a reservation is required for any reason, the Reservations Document must be included. Even though the event details are elsewhere, the need for a booking implies checking reservation policies. The next node might need to cross-reference both documents: events from one and booking requirements from the other. So, including the Reservations Document provides necessary context about booking requirements, even if the event info is in another document. Hence, the decision should be to include the Reservations Document here.
</think>
{
"reasoning": "The query asks about events that require booking. While event details are covered in the Upcoming Events Document, the requirement for booking inherently ties to reservation policies (e.g., whether reservations are mandatory for certain events, group handling, or reservation procedures). The reservations document provides critical context on policies that determine if an event requires a reservation, even if the event itself is listed elsewhere. Including it ensures the next node can verify if reservations are needed for events, aligning with the guideline to include reservations documents when booking intent is signaled.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I reserve a spot for any upcoming events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "Can I reserve a spot for any upcoming events?" I need to determine if the reservations document should be included.
First, the query mentions reserving a spot, which directly relates to reservations. The reservations document contains info on how to make reservations and policies around them. Even though upcoming events are covered in another document, the user is specifically asking about reserving a spot for those events. That implies they might need to know the reservation process or policies for events, which would be in the reservations document.
The crossover topics mention the upcoming events document includes event details and tickets, but the act of reserving a spot (like booking a table for the event) would involve the reservations document. Additionally, the guidelines state that if the query involves reservation actions, the document should be included. So even though the event info is elsewhere, the reservation aspect requires including the reservations document to address the booking intent.
</think>
{
"reasoning": "The query explicitly asks about reserving a spot for upcoming events. While event details fall under the 'upcoming events document', the act of reserving a spot involves reservation policies, procedures, and contextual requirements (e.g., group size handling, cancellation policies, or seating layouts for events). The reservations document is necessary to confirm whether reservations are possible for events, how they are managed, and to provide actionable steps for the user. This aligns with the guideline that reservation-related intent requires inclusion of the reservations document, even if other documents handle parts of the query.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any events that require a reservation?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "Are there any events that require a reservation?" The task is to determine if the reservations document should be included.
First, I need to check what's in the reservations document. It includes info on reservation policies, how to make or check reservations, and details like minimum spends, cancellation policies, and seating layouts. Also, it covers if reservations are needed for certain areas or events.
The query is about events needing reservations. The upcoming events document would list the events and their details, like dates and whether tickets are needed. But the part about whether a reservation is required might be in the events document or the reservations document.
Looking at the crossover topics, the events document covers event-specific policies. However, the user is asking if a reservation is required. The guidelines say that any query asking if a reservation is needed means the reservations document must be included. Even if the events document has event info, the requirement for a reservation might involve the reservation policies (like for certain areas or group sizes), which are in the reservations doc. The next node might need the reservations document to confirm if events require reservations based on venue policies. So, include the reservations doc here.
</think>
{
"reasoning": "The query asks whether any events require a reservation. While the upcoming events document would list event details, the reservations document contains policies about when reservations are mandatory (e.g., for reserved areas, group sizes, or time-limited slots). This context is critical to determine if an event-related reservation is needed, aligning with the guideline to include reservations documents when the query involves reservation requirements.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do I need to book tickets for any events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let me go through this step by step. The user is asking, "Do I need to book tickets for any events?" The task is to decide if the reservations document should be included.
First, I'll break down the query. The user is asking about booking tickets for events. The reservations document contains info on reservation policies, how to make reservations, and things like minimum spends or time limits. But wait, events are covered in the upcoming events document, right? That document has details on whether tickets are needed for specific events. So the answer about tickets for events would be there.
But the guidelines say that if the query is asking whether a reservation is required, even if part of the answer is in another document, the reservations document must be included. Wait, the user is asking about booking tickets for events. The upcoming events document would mention if tickets are needed and how to get them. But the reservations document might not directly answer that. However, the guidelines also mention that if the user is signaling booking intent, even if part of the answer is elsewhere, the reservations document should be included for context.
In this case, the user is asking if they need to book tickets. The reservations document includes info on how to make reservations and policies around them. But the actual need for tickets would be in the events document. However, since the query is about booking (which relates to reservations), the next node might need the reservations document to check policies, even if the main answer is in the events doc. For example, if an event requires a ticket, the next node might need to cross-check if a reservation is also needed through the reservations process.
Therefore, even though the primary info is in the upcoming events doc, the mention of booking tickets triggers the inclusion of the reservations document as per the guidelines. The reservation policies might be necessary context for the next node to fully answer whether booking is required, especially if events have associated reservations or seating arrangements that require booking.
</think>
{
"reasoning": "The user's query asks about booking tickets for events, which signals intent related to reservations or bookings. While event-specific ticket requirements are covered in the Upcoming Events document, the reservations document is necessary to provide context about reservation policies, procedures, or whether reservations are required for certain events. Including the reservations document ensures the next node can validate if reservations (beyond just tickets) are needed and how they interact with event access.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any upcoming events I should reserve?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break down the user's query: "Are there any upcoming events I should reserve?" The user is asking about upcoming events but specifically mentions reserving. The main task here is to determine if the reservations document is relevant.
First, the upcoming events are covered in their own document, which includes details like dates, times, and event specifics. However, the user's question includes the word "reserve," indicating they might need to make a reservation for these events.
Looking at the guidelines, if the query involves reservations, even if the core is about another topic (like events), the reservations document must be included. The reservations document contains policies on how to make reservations, minimum spends, cancellation policies, and procedures for checking reservations. Even though the events document has event info, the act of reserving is handled by the reservations doc.
Additionally, the next node might need to check if reservations are required for events or explain how to reserve, which relies on the reservations document. Without it, the response might miss crucial steps about booking for the events. Therefore, including the reservations document here is necessary to fully address the user's intent to reserve for the events.
</think>
{
"reasoning": "The query 'Are there any upcoming events I should reserve?' explicitly includes the keyword 'reserve,' indicating an intent to book or secure a reservation for an event. While event details are in the upcoming events document, the act of reserving or booking for an event requires context from the reservations document. This document contains policies (e.g., how to make reservations, time limits, cancellation rules) that are essential for confirming whether reservations are needed for events and how to act on them. Including the reservations document ensures the next node can address both the event inquiry and the reservation process.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do I need a booking for any of your events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's look at the query: "Do I need a booking for any of your events?" The user is asking whether a reservation is required for events.
First, I need to check if the question relates directly to reservations. The key term here is "booking," which is synonymous with reservation. The query is specifically about whether bookings are necessary for events.
Now, considering the crossover topics. The upcoming events document contains info on events, including whether tickets are needed. However, the query isn't just about event details; it's about needing a reservation for those events. The reservations document includes policies about reservations, including how events might require bookings.
The guidelines state that any query asking if a reservation is needed requires including the reservations document. Even if events are in another document, the need for a booking ties into reservation policies. Also, the next node might need the reservations document to confirm policies related to event bookings, like group handling or minimum spends.
Since the user is signaling intent related to booking (even for events), the reservations document is relevant here. The answer would depend on the venue's reservation policies for events, which are in the reservations document. Therefore, include it.
</think>
{
"reasoning": "The user is asking whether a booking is required for events, which directly ties to reservation policies and procedures. While events are covered in the upcoming events document, the question specifically involves determining if reservations are necessary (a core reservation policy matter). The reservations document contains details on reservation requirements, seating capacity for groups, and policies that might apply to event attendance (e.g., minimum spends, time limits). Including the reservations document ensures the next node can verify if events have reservation mandates or contextual requirements (e.g., group size limitations).",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are reservations required for any events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "Are reservations required for any events?" So first, I need to determine if the reservations document is relevant here. The reservations document includes info on whether reservations are needed, policies about reservations, and how to make them.
Now, looking at the crossover topics. The upcoming events document covers event details like dates, tickets, and event-specific rules. But the user is specifically asking about reservations for events. Even though events are in another document, the part about whether reservations are required isn't covered there. The upcoming events document might mention if an event needs a ticket, but not necessarily if a reservation at the venue is needed.
The guidelines say that if the query involves whether a reservation is required, the reservations document must be included. Even if events are in another doc, the reservation requirement is part of the reservation policies. So the next node would need the reservations document to check if events require reservations. Maybe some events have reservation policies like minimum spends or time limits mentioned in the reservations doc.
Also, the user is signaling intent related to booking or reserving by asking if reservations are needed. According to the system message, even if the core is about events, the reservation intent means we include the reservations doc. So the decision is to include it.
</think>
{
"reasoning": "The query asks whether reservations are required for events. While event details are covered in the **upcoming events document**, the question specifically probes reservation requirements. The **reservations document** contains policies about when reservations are necessary (e.g., for reserved areas, time limits, group handling) and whether events might impose reservation rules. This document is critical to verify if any events mandate reservations, even if event descriptions themselves reside elsewhere. The user’s mention of 'reservations required' directly signals booking intent, necessitating inclusion for context.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I book tickets for upcoming events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break down the query: "Can I book tickets for upcoming events?" The user is asking about booking tickets for events. Now, according to the crossover topics, upcoming events are covered in their own document, which includes information like event dates, times, tickets needed, etc. However, the user specifically mentions "book tickets," which implies an action related to making a reservation or booking.
The reservations document includes information on how to take action to make a reservation. Even though the events themselves are detailed in the upcoming events document, the act of booking tickets might involve reservation policies or procedures. Also, the guidelines state that if there's any mention of booking or reservations, the reservations document should be included to provide context, even if the core info is elsewhere. Since the user is asking about booking (which is an action related to reservations), the reservations document is needed to ensure the next node can address the booking process correctly, even if the event details are in another document. Therefore, include the reservations document.
</think>
{
"reasoning": "The user's query about booking tickets for upcoming events involves an action related to reservations (i.e., 'booking'). While event details are covered in the Upcoming Events document, the reservations document is required to provide context on reservation policies, procedures, or how to take action (e.g., making a reservation). The mention of 'book' signals reservation intent, necessitating inclusion of the reservations document to support the next node in addressing the booking process.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Is there an event I need to reserve in advance?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "Is there an event I need to reserve in advance?" The key here is determining if the reservations document is relevant. First, I need to check if the query relates to reservation policies or procedures. The user is asking about events requiring reservations. The upcoming events document would list event details, including whether a ticket is needed, but the part about needing a reservation in advance might involve the reservation policies.
Looking at the reservations document's contents, it includes info on how to make reservations, policies like cancellation, and handling of groups. Even though the event details are in the upcoming events doc, the need to reserve in advance likely ties into the reservation policies (like how to book, time limits, etc.). Also, the guidelines mention that if the query asks whether a reservation is required, the reservations doc should be included to provide context on policies. So even if the event info is elsewhere, the reservations doc is needed to confirm if reservations are necessary and how to handle them.
</think>
{
"reasoning": "The query asks whether an event requires advance reservation. While event details are covered in the upcoming events document, the question directly ties to reservation requirements and booking procedures. The reservations document includes policies about reservation necessity, time limits, and procedures for making bookings, which are critical to confirm if reservations are mandatory for specific events. This aligns with the guideline to include the reservations document when queries involve reservation requirements or booking intent, even if event details reside elsewhere.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are any upcoming events reservation-only?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break down the query: "Are any upcoming events reservation-only?" The user is asking if any of the upcoming events require reservations.
First, I need to check which documents are relevant. The Upcoming Events document contains details about events, including whether tickets are needed. However, the question isn't just about the events themselves but specifically if reservations are required. The Reservations document includes policies related to reservations, such as whether certain areas or events require them. Even though the Upcoming Events document might mention ticket requirements, the necessity of a reservation (as opposed to a ticket) could be covered in the Reservations document's policies. Additionally, since the query involves the need for reservations, which is a key part of the Reservations document's content, including it would provide necessary context for the next node to accurately determine if events are reservation-only. Therefore, the Reservations document should be included.
</think>
{
"reasoning": "The query asks whether upcoming events require reservations. While event details are in the Upcoming Events document, the reservation policy (whether events are reservation-only) is covered in the Reservations document. The query explicitly involves reservation requirements, necessitating inclusion of the Reservations document to address reservation policies for events.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you have any events that require advance booking?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's see. The user is asking, "Do you have any events that require advance booking?" First, I need to determine if the reservations document is relevant here.
The query is about events that need advance booking. The upcoming events document would handle event details like dates, times, and if tickets are needed. But the key here is the "require advance booking" part. This implies whether reservations or bookings are necessary for those events.
The reservations document includes policies on reservations, how to make them, and possibly any event-specific reservation requirements. Even though the events themselves are in another document, the need for booking relates to reservation policies. The guidelines say if the query involves whether a reservation is required, the reservations document must be included to provide context on policies and procedures.
So even though the events are in a different document, the part about requiring advance booking ties into reservation policies, so including the reservations document helps the next node check if those events do need reservations and explain how to make them. Therefore, the decision is to include the reservations document.
</think>
{
"reasoning": "The query asks about events requiring advance booking, which implies a need to understand reservation policies. While event details are covered in the upcoming events document, determining whether reservations are required or how they're handled for events directly relates to the reservations document's contents about reservation policies, booking procedures, and event-specific requirements. Including the reservations document ensures the next node can verify if reservations are mandatory for events and provide actionable steps for booking.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there events that require pre-booking?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "Are there events that require pre-booking?"
First, I need to determine if the reservations document is relevant here. The reservations document includes info on reservation policies, how to make reservations, and any requirements like minimum spends or time limits.
The query is about events needing pre-booking. The upcoming events document (crossover topic) might list events, including whether they require tickets. However, the user specifically mentions "pre-booking," which sounds like it's about reservations. The reservations document would detail if certain events (like special ones) require a reservation. Even though the events are covered in another document, the necessity of pre-booking ties into reservation policies.
The guidelines say if the query involves whether a reservation is required, include the reservations document. Also, even if the core info is in another doc, if reservations are part of the requirement, it's needed. The next node might need reservation policies to confirm if events need booking. So, include reservations doc here.
</think>
{
"reasoning": "The query asks whether events require pre-booking, which directly implicates reservation requirements. While the *specific event details* are covered in the upcoming events document, determining if reservations or bookings are *required* for those events would rely on policies and procedures documented in the reservations document (e.g., cancellation policies, group handling, or reservation mandates for certain areas). Additionally, the guidelines specify that if a query involves whether a reservation is required, even indirectly, the reservations document must be included to provide context for the next node to validate requirements.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Should I book in advance for any events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break down the user's query: "Should I book in advance for any events?" The user is asking whether they need to make a reservation for events.
First, I check the reservations document contents. It includes policies on reservations, how to make them, and handling groups or large bookings. The query is about booking for events, so I need to see if the events info is handled here.
Looking at the crossover topics, the Upcoming Events document covers event details like dates, tickets, and event-specific policies. However, the user isn't asking about event details themselves but whether booking is needed. The reservations document would cover if reservations are required for events, even if the event specifics are elsewhere.
The guidelines state that if the query is about whether a reservation is required, the reservations document should be included. Even though events are in another document, the need to book in advance relates to reservation policies, which the reservations document addresses. So including it provides context on reservation requirements for events.
</think>
{
"reasoning": "The query asks whether booking in advance is necessary for events. While event details are covered in the Upcoming Events document, the question explicitly involves reservation intent ('book in advance'). The reservations document contains policies about reservations, cancellation rules, and how events might require bookings (e.g., reserved areas with minimum spends or time limits). Including the reservations document ensures the next node can address whether reservations are required for events and provide relevant booking policies.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Is booking necessary for any of your events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Alright, let's break this down. The user is asking, "Is booking necessary for any of your events?" The task is to determine if the reservations document should be included in the context for answering this query.
First, I need to check if the query relates to reservations or booking. The key terms here are "booking" and "events." The user wants to know if reservations are required for events.
Looking at the reservations document contents, it includes policies about reservations, how to make them, and possibly any requirements like minimum spends or time limits. The upcoming events document would cover event details, including whether a ticket is needed. However, the question isn't just about event existence but specifically about the necessity of booking, which ties into reservation policies.
The guidelines mention that if the query asks whether a reservation is required, even if the event details are in another document, the reservations document must be included. This is because the reservations document provides context on policies, like if events require reservations or have specific booking procedures.
Even though event information is in the upcoming events document, the necessity of booking likely relates to the venue's reservation policies. For example, some events might require tickets (covered in events doc), but others might need a reservation through the venue's system (covered here). The next node would need the reservations document to confirm if bookings are necessary and what the policies are.
The crossover topics in other documents don't address reservation requirements for events. Therefore, the reservations document is relevant here because the query directly involves booking necessity, which is part of the reservation policies.
</think>
{
"reasoning": "The query asks whether booking is necessary for events, which directly relates to reservation requirements. While event details are covered in the UPCOMING EVENTS document, the necessity of reservations or bookings for accessing events falls under reservation policies. The reservations document includes information about reservation requirements for reserved areas, group handling, and policies that might apply to event attendance. Including this document ensures the next node can verify if events require reservations or have associated booking rules (e.g., minimum spends, time limits) even if the event itself is described elsewhere.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do I have to reserve tickets for any events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's look at the user's query: "Do I have to reserve tickets for any events?" They're asking if reserving tickets is necessary for events.
First, I check the crossover topics. The Upcoming Events document covers event details, including whether tickets are needed. But the user specifically mentions reserving tickets, which implies a reservation process. The Reservations document includes policies on reservations, like how to make them and whether they're required. Even though event tickets are in the Events document, the act of reserving ties into the Reservations document's policies.
The guidelines say to include Reservations if the query involves needing a reservation. Since the user is asking if they "have to reserve tickets," this directly relates to reservation requirements, which are in the Reservations document. The next node might need that info to confirm policies, even if events are handled elsewhere. So, include Reservations.
</think>
{
"reasoning": "The query asks whether reservations are required for events. While event-specific ticket requirements are covered in the Upcoming Events document, the reservations document contains critical context about reservation policies (e.g., whether reservations are mandatory for certain areas/events, time limits, or cancellation rules). Including the reservations document ensures the next node can cross-reference reservation policies with event requirements, as the user explicitly mentions 'reserve tickets'—a signal of booking intent.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there events I need to pre-book?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "Are there events I need to pre-book?" The task is to decide if the reservations document should be included in the context for answering this query.
First, I need to check what's in the reservations document. It contains info on reservation policies, seating layouts, how to make or check reservations, and policies about groups or large bookings. So if the question is about needing reservations for events, the document might have relevant info on whether pre-booking is required.
Next, looking at the crossover topics. The upcoming events document handles event specifics, dates, tickets, etc. But the user isn't just asking about events; they specifically mention pre-booking. The question implies they want to know if reservations are necessary for attending events.
The guidelines say that if the query asks whether a reservation is required for any reason, the reservations document must be included. Even though events are covered in the upcoming events document, the need to pre-book relates directly to reservation policies. The reservations document would provide context on policies like minimum spends, time limits, or procedures for booking, which are essential to determine if pre-booking is needed for events.
Additionally, the next node might need the reservations document to check if events require reservations, even if the events themselves are detailed elsewhere. Since the user is signaling an intent related to booking (pre-book), including the reservations document ensures the next node has all necessary context about reservation requirements and procedures.
</think>
{
"reasoning": "The query asks about events requiring pre-booking, which directly ties to whether reservations are necessary. While event details are covered in the 'upcoming events document', the need for pre-booking inherently relates to reservation policies (e.g., whether events require tickets, group bookings, or reserved areas with minimum spends). The reservations document includes policies about reservations for large groups, time limits, and booking procedures, all of which are critical context for determining if events require advance reservations. Additionally, the user signals booking intent (pre-book), which mandates including the reservations document to ensure the next node can verify reservation requirements alongside event details.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do I need to make a reservation for any future events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let me break this down. The user is asking, "Do I need to make a reservation for any future events?" The task is to determine if the reservations document should be included.
First, the reservations document includes info on reservation policies, like whether reservations are needed. The query is explicitly about needing reservations for future events. The upcoming events document might have event details, but the question is whether a reservation is required.
Looking at the crossover topics, the upcoming events document has event info but not reservation policies. The reservations document would cover if reservations are necessary for events. Since the user is asking about the need to reserve for events, even though events are covered elsewhere, the key point here is the reservation requirement.
The guidelines say that if the query is about needing a reservation, include the reservations doc. Even if the event details are in another document, the reservation requirement is in reservations. So, the answer depends on reservation policies, which are in the reservations document. Therefore, include it.
</think>
{
"reasoning": "The query explicitly asks whether a reservation is required for future events. While event details are covered in the 'upcoming events' document, the core of this query relates to reservation policies and requirements. The reservations document contains information on whether reservations are needed (e.g., for reserved areas, policies for events requiring bookings, or general reservation requirements). Even if the answer ultimately references event-specific policies, the reservations document is critical to determine the necessity of reservations as part of the response framework.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any bookable events coming up?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "Are there any bookable events coming up?" The key terms here are "bookable events." Now, I need to check if the reservations document is relevant for this query.
First, the reservations document contains info on reservation policies, how to make or check reservations, and details about seating and group handling. The upcoming events document, which is separate, lists events with dates, times, ticket info, etc. The query is about events that can be booked, which might mean tickets or reservations.
But wait, the user specifically mentions "bookable," which implies some form of reservation or booking. Even though the events themselves are in the upcoming events document, the act of booking might require checking if reservations are needed for these events. The reservations document includes policies on reservations, which could tie into whether an event requires a reservation.
The guidelines say that if the query is about whether a reservation is required, the reservations document must be included. Here, "bookable" suggests that the events require some form of booking, so the next node might need the reservations document to confirm if reservations are necessary for those events. Even if the event details are in another document, the booking aspect crosses into reservations policies. So, including the reservations document provides context on how to book or if it's needed, even if the event info is elsewhere.
</think>
{
"reasoning": "The query 'Are there any bookable events coming up?' implies a need to understand whether reservations or bookings are required or available for upcoming events. While event details (dates, descriptions) are in the Upcoming Events document, the term 'bookable' signals intent related to reservation/booking policies. The Reservations Document is required to provide context on reservation procedures, policies (e.g., time limits, cancellation rules), and whether reservations are even possible for events, which is critical for the next node to address the 'bookable' aspect of the query.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
How do I reserve a ticket for upcoming events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking how to reserve a ticket for upcoming events. First, I need to check if the reservations document is relevant here. The reservations document contains info on how to make reservations, including policies and procedures. The query mentions reserving tickets, which implies booking or reservation intent.
Now, looking at the crossover topics, the upcoming events document handles event details, including whether tickets are needed. However, the actual process of reserving a ticket—how to make that reservation—isn't covered there. The reservations document includes information on how to take action, like making a reservation. Even though events are mentioned, the core of the query is about the reservation process itself, which falls under the reservations document's scope.
The guidelines state that if the query involves making a reservation, even for an event, the reservations document should be included. Additionally, the next node might need the reservations document to provide context on procedures. So, even if the event details are in another document, the action of reserving a ticket requires the reservations document to explain how to do it. Therefore, including it is necessary here.
</think>
{
"reasoning": "The query explicitly asks about reserving tickets for upcoming events, which signals a booking/reservation intent. While event details (date, time, ticket requirements) are covered in the Upcoming Events document, the **process to reserve tickets** (how to take action) falls under the Reservations document's scope. The Reservations document provides context on policies and procedures for making reservations, which is critical to answering the *how* of ticket reservation, even if event-specific rules are in another document. Additionally, the next node may need the Reservations document to confirm whether reservations are required for events or to explain the booking process.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any limited-seat events I should book?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "Are there any limited-seat events I should book?" The key parts here are "limited-seat events" and "book." The task is to determine if the reservations document should be included.
First, the query mentions events, which might be in the Upcoming Events document. That document covers event details like dates, times, and whether tickets are needed. However, the user is specifically asking about booking these events. The action of booking or reserving ties into the reservations document because even if the event details are in another document, the need to book implies checking reservation policies or procedures.
Looking at the reservations document contents, it includes info on how to make reservations, policies on group bookings, and minimum spends—things that could affect booking a limited-seat event. The guidelines say that if the query involves reservation policies or needing a reservation, the document should be included. Even though the event details are elsewhere, the act of booking requires the reservations context for procedures or policies. Plus, the next node might need reservation info to verify if booking is necessary for these events.
</think>
{
"reasoning": "The user's query asks about 'limited-seat events I should book,' which explicitly involves booking/reservation intent. While event details are covered in the Upcoming Events document, the inclusion of 'book' signals a need to reference reservation policies, procedures, or capacity limitations (e.g., seat availability, reservation requirements for events). The reservations document contains critical context about reservation actions (how to book) and policies (minimum spends, group handling) that may apply to limited-seat events. Even if event-specific rules exist in another document, the reservations document is necessary to address the booking aspect of the query, ensuring the next node can validate reservation-related constraints.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I make a reservation for any events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's analyze this query: "Can I make a reservation for any events?"
First, the user is asking about making a reservation specifically for events. The reservations document includes information on how to take action to make a reservation. While the events themselves are detailed in the Upcoming Events document, the act of reserving a spot for an event would involve the reservations process.
The crossover topics mention that events are in the Upcoming Events document, but the question is about the reservation process for those events. Since the reservations document covers how to make reservations, even if the event details are elsewhere, the reservation policies and procedures are needed here.
Additionally, the guidelines state that if the query involves reservation actions, the document should be included. The user is directly asking about making reservations, which is a core part of the reservations document. Even though the event info is in another document, the reservation aspect requires this document's context.
So the decision is to include the reservations document because the query explicitly involves making a reservation, even if it's related to events handled in another document.
</think>
{
"reasoning": "The query asks about making reservations for events. While event details are covered in the Upcoming Events document, the reservations document contains critical information about reservation policies, procedures, and action-oriented steps for booking. Since the user explicitly mentions reservation intent ('make a reservation'), the reservations document is necessary to provide context about how reservations are handled, even if event specifics reside elsewhere. The guidelines mandate inclusion when reservation actions or policies are involved.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do I need to book a spot for any events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break down the query: "Do I need to book a spot for any events?" The user is asking if booking is required for events.
First, check the reservations document's contents. It includes info on reservation policies, which would cover whether bookings are needed. The events document (upcoming events) might have event-specific details, but the question is about whether a reservation is necessary. The reservations doc handles policies like when reservations are required, time limits, minimum spends, etc.
Looking at crossover topics, the events document covers event dates and tickets but not the need for reservations. The user's query isn't about event details but whether booking is needed. The guidelines state that if the query asks if a reservation is required, include the reservations doc. Even if events are mentioned, the core is about booking necessity, which the reservations doc addresses. So, include it.
</think>
{
"reasoning": "The user is asking whether a booking is required for events. While the events document might cover details about specific events, the question specifically involves determining if reservations are necessary. The reservations document contains policies about when reservations are required, including for events, and whether there are specific conditions (e.g., minimum spends, time limits) tied to bookings. Including the reservations document ensures the next node can verify if events at the venue typically require reservations and communicate relevant policies.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are any events reservation-based?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's tackle this query: "Are any events reservation-based?" I need to determine if the reservations document should be included.
First, the user is asking about events requiring reservations. The events themselves are covered in the upcoming events document, which lists details like dates and whether tickets are needed. But the key here is whether reservations (a separate concept from tickets) are required for these events. The reservations document includes policies like minimum spends, time limits, and how groups are handled.
Even though events info is in another document, the question is about whether reservations are needed for events. The upcoming events document might mention if a ticket is needed but not necessarily reservation policies. The reservations document would outline if certain events require reservations, especially for seating or group bookings.
Also, the guidelines state that if the query involves whether a reservation is required, include the reservations document. Even if the main answer comes from another document, the reservations doc provides context on reservation policies relevant to events. So including it helps the next node verify if events have reservation requirements beyond just tickets.
</think>
{
"reasoning": "The user's query asks whether events require reservations. While event details are found in the upcoming events document, the reservations document contains critical context about reservation policies (e.g., whether reservations are mandatory for event participation, group handling, or seating allocation). Including the reservations document ensures the next node can verify if reservations are tied to event access, even if the primary event description resides elsewhere.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are any of your events ticketed and require booking?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's analyze this query: "Are any of your events ticketed and require booking?" The user is asking about events that need tickets and booking. First, I need to check if the reservations document is relevant here.
The reservations document contains info on reservation policies, how to make or check reservations, seating layouts, and opening hours. However, the query is about events requiring tickets and booking. The Upcoming Events document specifically covers event details including whether a ticket is needed and booking requirements. Since the Upcoming Events document has this info, the core answer lies there.
But the guidelines mention that even if the query isn't solely about reservations, if it involves needing a reservation or booking, the reservations document should be included for context. Here, the user mentions "require booking," which relates to whether reservations are needed for events. The next node might need reservation policies (like how to book or cancellation rules) to fully answer, even if the main info is in Upcoming Events. Hence, include the reservations document to provide necessary context about booking procedures.
</think>
{
"reasoning": "The query asks whether events require booking, which directly relates to reservation policies and procedures. While event-specific ticketing details are covered in the Upcoming Events document, the mention of 'require booking' necessitates checking reservation requirements and booking processes. The reservations document contains essential context about reservation policies (including how to book and whether reservations are necessary), which the next node needs to validate even if the core event information resides elsewhere. Including the reservations document ensures the response addresses both ticketing and booking dependencies.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Is a reservation needed for any scheduled events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's tackle this query: "Is a reservation needed for any scheduled events?"
First, I need to check if the question relates to the contents of the reservations document. The reservations document includes policies like whether reservations are required, cancellation policies, how groups are handled, etc. It also mentions information about seating layouts and how to make or check reservations.
The query is asking if reservations are necessary for scheduled events. Now, the upcoming events document covers details about events, including dates, times, tickets, and event-specific rules. However, the user is specifically asking about whether a reservation is needed.
Even though event details are in the upcoming events document, the part about whether a reservation is required would relate to the venue's reservation policies. The reservations document includes policies on when reservations are needed, such as for certain group sizes or areas with minimum spends. Additionally, if the event requires a reservation (e.g., for seating or special arrangements), that information might be tied to the venue's general reservation policies covered in the reservations document.
Moreover, the guidelines state that any query asking whether a reservation is needed requires including the reservations document. Even if events are handled in another document, the need for a reservation would depend on the policies in the reservations document. The next node might need to cross-reference both the events and reservations documents to determine if reservations are necessary for those events.
Therefore, including the reservations document here is appropriate because it provides essential context about reservation requirements, even if the event details are elsewhere.
</think>
{
"reasoning": "The query asks whether reservations are needed for scheduled events. While event details are covered in the 'upcoming events' document, determining if a reservation is required ties directly to reservation policies (e.g., event-specific booking rules, group handling, or time limits). The reservations document contains essential context about when reservations are mandatory, even if event specifics are elsewhere. Including it ensures the next node can verify reservation requirements aligned with the venue's policies.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I pre-book tickets for your events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's analyze this query. The user is asking if they can pre-book tickets for events. First, I need to determine if the reservations document is relevant here. The reservations document includes info on making reservations, checking them, and policies around bookings. But the query is about event tickets.
Looking at the crossover topics, the upcoming events document handles event details, including whether tickets are needed. However, the user is specifically asking about pre-booking tickets. Pre-booking might imply a reservation process. Even though the events document has ticket info, the action of booking tickets might require the reservations document's procedures.
The guidelines mention that if the query involves actions like making a reservation or booking, even if part of the answer is in another document, the reservations document should be included for context. Since pre-booking tickets could involve reservation policies or procedures (like how to make a reservation for an event), the next node might need the reservations document to confirm how bookings are handled, even if the event details are elsewhere.
Also, the reservations document includes how to take action on behalf of the customer, like making a reservation, which aligns with pre-booking tickets. Therefore, including the reservations document provides necessary context for the next node to address both the event ticket availability and the booking process.
</think>
{
"reasoning": "The query asks about pre-booking tickets for events. While the upcoming events document contains event-specific details (e.g., ticket requirements), the reservations document is critical to address the **action-oriented intent** of 'pre-booking.' Reservations policies and procedures (e.g., how to make reservations, check availability, or handle bookings) are directly relevant to processing ticket pre-orders, even if event specifics reside in another document. The next node will need reservations-related context to confirm whether pre-booking is possible and how it works.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any exclusive events that require reservations?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break down this query: "Are there any exclusive events that require reservations?" The user is asking about exclusive events that might need a reservation. First, I need to check which documents are relevant.
The Upcoming Events document contains info about special events, including whether tickets are needed. But the query also mentions "require reservations." While events might be covered in the Upcoming Events document, the part about needing reservations touches on reservation policies.
According to the guidelines, if the query involves whether a reservation is required, even if the main topic is events, the reservations document must be included. The reservations document has info on policies like when reservations are necessary, minimum spends, or how bookings are handled. Even though the events themselves are in another document, the requirement for reservations would involve checking the reservations policies.
Also, the next node might need the reservations document to confirm if those events have reservation requirements, even if the event details are elsewhere. So even if the answer is in the Upcoming Events doc, the reservation policies context is needed. Therefore, include the reservations document.
</think>
{
"reasoning": "The query asks about exclusive events that require reservations. While event details are covered in the Upcoming Events document, the mention of reservations needing to be required directly triggers the need to reference reservation policies and procedures. The Reservations Document contains critical context about when reservations are necessary (e.g., for reserved areas, large groups, or specific policies tied to events). Even if the event itself is described elsewhere, the Reservations Document is required to confirm whether reservations are mandated for such events, aligning with guidelines that mandate inclusion when reservation requirements are part of the query.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
How do I book a ticket for an event here?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's tackle this query. The user is asking, "How do I book a ticket for an event here?" First, I need to figure out if the reservations document is relevant here. The reservations document includes info on making reservations, checking them, and policies related to that.
Now, looking at the crossover topics: events are covered in the upcoming events document, which includes details about tickets and event-specific rules. But the user is specifically asking about booking a ticket. The upcoming events document might list if a ticket is needed and event details, but the actual process of booking a ticket isn't covered there.
Wait, the reservations document includes "how to take action on behalf of the customer to make a reservation." But booking a ticket for an event might be different. However, the next node might need the reservations document to check if there's a reservation required for the event or if the ticket booking is handled through reservations. Since the user mentions "book a ticket," there's an intent to take an action similar to making a reservation. The reservations document's info on making reservations could be part of the process, even if it's for an event.
Also, the guidelines mention if there's any reservation-related intent, include the document. Even if the core answer is in another document, the reservations document provides context. So here, booking a ticket might involve reservation policies or procedures, so including the reservations document is necessary for the next node to provide accurate info.
Therefore, the decision is to include the reservations document.
</think>
{
"reasoning": "The query asks about booking a ticket for an event, which signals an intent to take action related to reservations or bookings. While event-specific ticket details are in the 'upcoming events' document, the reservations document includes actionable steps for making reservations and context about reservation policies. The next node would require this document to ensure alignment with reservation procedures (e.g., whether event tickets are linked to reservations, cancellation policies, or group booking rules).",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any events that require an advance reservation?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "Are there any events that require an advance reservation?" First, I need to determine if the reservations document is relevant here. The query mentions events and whether they require reservations.
The Upcoming Events Document includes information about events, including whether a ticket is needed. But the user is specifically asking about reservations, which might overlap with policies mentioned in the Reservations Document. Even though events are covered in their own document, the part about requiring a reservation could relate to reservation policies, like how the venue handles bookings for events. The guidelines say that if the query is asking whether a reservation is required, the reservations document must be included to provide context about policies. So even if the events document lists events, knowing if those events need a reservation might involve checking the reservation policies, like minimum spends or time limits for event bookings. Therefore, including the reservations document here gives the necessary context about reservation requirements, even if the event details are elsewhere.
</think>
{
"reasoning": "The query asks whether events require advance reservations. While event details are in the Upcoming Events Document, the question specifically focuses on reservation requirements. The Reservations Document contains policies on reservations, including whether reservations are needed for certain scenarios (e.g., large groups, special events). Including it provides context on reservation policies that may apply to events, ensuring the next node can verify if reservations are mandatory for specific event types or capacities.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do I need to reserve my place for any events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let me start by analyzing the user's query: "Do I need to reserve my place for any events?"
The user is asking whether reservations are required for events. The first thing I need to check is which document would contain the information needed to answer this. The reservations document includes policies about when reservations are necessary, such as time limits, minimum spends, and handling of groups. The upcoming events document, however, details specific events and whether tickets are needed, but the query isn't just about events—it's about whether reserving a place is required for those events.
Looking at the crossover topics, the events are covered in the upcoming events document, which might mention if tickets are required, but the reservation policies (like whether you need to book a table or area for an event) would be in the reservations document. The user is specifically using the word "reserve," which implies booking a spot, possibly in the venue during an event. The reservations document's content about reservation requirements for different scenarios, including events, would be relevant here.
Even though events are in another document, the core of this query is about needing a reservation, which falls under the reservations document's policies. Also, the guidelines state that if the query is asking whether a reservation is required for any reason, the reservations document must be included. Therefore, to answer whether reserving a place is necessary for events, the reservations document should be included to provide context on reservation policies related to events.
</think>
{
"reasoning": "The query directly asks whether reservations are required for events. While events are covered in the upcoming events document, the question specifically concerns the necessity of reservations, which falls under the reservation policies in the reservations document. The reservations document includes details on policies like time limits, cancellation rules, and seating requirements that determine when reservations are mandatory. Additionally, the guidelines state that queries about reservation requirements for any reason (including events) must include the reservations document to evaluate policies. Even if event-specific details exist elsewhere, the reservations document is necessary to confirm whether reserving a place is required.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I book a seat at any upcoming events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "Can I book a seat at any upcoming events?" First, I need to check if the reservations document is relevant here.
The query mentions "book a seat" which directly relates to making a reservation. The reservations document includes information on how to make reservations and policies around bookings. Even though the user is asking about upcoming events, which are covered in the Upcoming Events Document, the action of booking a seat implies a reservation is needed.
Looking at the crossover topics, the Upcoming Events Document contains event details like dates and whether tickets are needed, but the actual process of booking a seat (reservation) would be in the Reservations Document. The user's intent to book triggers the need to include the reservations document, as it provides the necessary context on how to make that reservation, even if event specifics are elsewhere. Additionally, the guidelines state that any mention of reservations or bookings means including the Reservations Document. Therefore, even though the event details are elsewhere, the booking aspect requires the Reservations Document.
</think>
{
"reasoning": "The query 'Can I book a seat at any upcoming events?' explicitly mentions 'book a seat,' indicating reservation intent. While upcoming events are covered in the Upcoming Events Document, the action of booking a seat requires the Reservations Document to address reservation policies, procedures, or requirements (e.g., how to make reservations, check availability, or whether reservations are necessary for events). The reservations document is needed to confirm if reservations are applicable to events and to provide context for the next node to verify booking-related details.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are reservations open for any of your events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "Are reservations open for any of your events?" The key here is the mention of reservations and events.
First, I check the reservations document's contents. It includes info on making reservations, checking them, and policies like cancellations. The events are covered in the upcoming events document, which has event dates, tickets, etc. But the user is specifically asking about reservations being open for events.
Even though event details are in another document, the query is about reservation availability for those events. The reservations document is needed to confirm if reservations can be made for events, how to do it, and any related policies. Even if the events info is elsewhere, the act of reserving requires the reservations doc. The guidelines say if the query involves reservations, even if part of an event, include it. So the decision is include.
</think>
{
"reasoning": "The query asks about reservations being open for events. While event details are covered in the upcoming events document, the reservations document is required to address the reservation-specific aspect (e.g., whether reservations are accepted for events, how to make them, or associated policies). The mention of 'reservations' directly signals booking intent, necessitating context from the reservations document to answer fully.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any special events that require a reservation?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break down the query: "Are there any special events that require a reservation?" The user is asking about special events, which are covered in the upcoming events document. However, they specifically mention "require a reservation," so even though events are in another document, the part about needing a reservation is about reservation policies. The reservations document includes info on whether reservations are needed for certain areas or events, like minimum spends or time limits. Also, the guidelines state that if the query asks if a reservation is required, even if the main topic is events, the reservations document should be included. The next node might need both the events info and the reservation policies to answer properly. So, include the reservations document here.
</think>
{
"reasoning": "The query asks whether special events require a reservation. While the upcoming events document contains event details, the mention of reservation requirements directly invokes reservation policies (e.g., whether reservations are mandatory for events, cancellation rules, or group handling). The reservations document is needed to address the reservation-related aspect of the query, as it governs policies tied to events. Additionally, even if the answer ultimately depends on event-specific rules, the reservations document provides critical context for the next node to verify reservation policies in conjunction with event details.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do any events require prior booking?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "Do any events require prior booking?"
First, I need to figure out if the reservations document is relevant here. The reservations document includes info on reservation policies, how to make reservations, and whether bookings are needed. The query is about events needing prior booking.
Now, looking at the crossover topics: the upcoming events document has info on events, including whether tickets are needed. But the user specifically mentions "prior booking," which implies reservations. While the events document might list ticket requirements, the act of booking or reserving a spot for an event could involve the reservation policies.
The guidelines say that if the query involves whether a reservation is required, the reservations document must be included. Even though events are covered in another document, the need for prior booking ties into reservation policies. Therefore, including the reservations document provides context on how bookings work for events, even if the events themselves are detailed elsewhere.
Additionally, the next node might need to check if reservations are possible for events, which the reservations document can help with. So, despite the events being in another document, the reservation aspect makes it necessary to include the reservations document here.
</think>
{
"reasoning": "The query asks whether any events require prior booking. While event details are covered in the 'upcoming events' document, determining if a reservation is needed ties directly to reservation policies (e.g., whether bookings are mandatory for specific events, how reservations are handled). The reservations document includes policies on reservations for events, minimum spends for reserved areas, and actions related to making reservations, which are critical to address the 'prior booking' aspect. Even if the event details are elsewhere, the need to reference reservation procedures and policies justifies including this document for context.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do I need to book ahead for any events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let me break this down. The user is asking, "Do I need to book ahead for any events?" The task is to decide if the reservations document should be included.
First, check if the query is about reservations. The user is asking whether booking is required for events, which directly relates to reservation policies. The reservations document contains info on reservation policies, including whether reservations are needed for certain scenarios.
Now, look at the crossover topics. The upcoming events document handles event details, like dates and whether tickets are needed. But the user isn't just asking about event details; they're specifically asking if booking (reserving) is required. The reservations document would have info on if events require reservations, even if the events themselves are detailed elsewhere.
The guidelines say to include the reservations document if the query involves whether a reservation is required. Even though events are in another document, the need to book ahead would be covered by reservation policies. So the reservations document is needed to answer the booking requirement part.
Therefore, the decision is to include the reservations document.
</think>
{
"reasoning": "The query asks whether booking is required for any events. While event details are covered in the upcoming events document, the need to book ahead relates directly to reservation policies. The reservations document contains information on reservation requirements, including policies for events that might necessitate advance booking. The document is needed to determine if reservations are mandatory or recommended for specific events, even if event specifics are in another document.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there events with limited booking spots?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's analyze the query: "Are there events with limited booking spots?" The user is asking about events that have a restriction on the number of available spots for booking.
First, I need to check if the reservations document is relevant here. The reservations document includes info on reservation policies, how groups are handled, and actions like making reservations. However, the query is about events with limited spots, which falls under the upcoming events document, as that document covers event-specific details like ticket requirements and event policies.
But wait, the guidelines mention that even if the core is elsewhere, if the query involves whether a reservation is required or booking-related aspects, the reservations document should be included. The user is asking about "limited booking spots," which implies that booking (reservations) might be necessary for these events. Even though event details are in another document, the next node might need to reference reservation policies to answer if reservations are needed or how booking works for these events.
The crossover topics include the upcoming events document, but since the query involves booking spots, which relates to reservations, the reservations document should be included. The next node might need to check if events require reservations, their availability, or how bookings are handled, which is covered in the reservations document. Therefore, including it provides necessary context.
</think>
{
"reasoning": "The query asks about events with limited booking spots, which implies a need to understand reservation availability and policies for events. While event details are covered in the upcoming events document, the mention of 'booking spots' directly ties to reservation capacity and procedures. The reservations document includes information on reservation policies, handling of group bookings, and actions like checking or making reservations, which are necessary context to address whether event bookings are limited and how they are managed.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do I need to reserve a table or ticket for an event?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let me break down the user's query: "Do I need to reserve a table or ticket for an event?" The user is asking if reservations are required, either for a table (which relates to dining) or for an event ticket.
First, checking the reservations document's contents, it includes policies about reservations, walk-ins, and how events might require reservations. The part about events needing reservations might be covered in the reservations document, especially if there's info on whether events require tickets or prior booking. However, the upcoming events document details event-specific policies, including whether a ticket is needed. But the user is combining both a table reservation and event tickets in one question.
According to the guidelines, if the query asks if a reservation is needed, even if part of it relates to events (which might be in another document), the reservations document must be included. The reasoning here is that the core of the query is about whether a reservation is necessary, which directly relates to the reservations document's policies. Even if part of the answer might come from the events document, the reservations document is still relevant for the reservation aspect, especially for tables. Since the user mentioned both, including the reservations document provides necessary context on table reservations, even if events are covered elsewhere. The next node might need info from both documents to answer fully, but the reservations document is definitely needed here.
</think>
{
"reasoning": "The query directly asks whether a reservation is required for a table or event. The reservations document contains policies about reservation requirements, including context on when reservations are necessary (e.g., for events, walk-ins, group sizes, etc.). Even though event-specific ticket policies may overlap with the upcoming events document, the query explicitly ties reservations to both tables and events, making the reservations document essential to confirm policies and provide context for the next node's response.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any upcoming events that require booking a ticket?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's see. The user is asking about upcoming events that require booking a ticket. First, I need to check if the reservations document is relevant here.
The query mentions "require booking a ticket," which implies reservations or bookings. The reservations document includes info on how to make reservations and check them, as well as policies about events needing reservations. Even though the upcoming events document has details on whether tickets are needed, the part about requiring a booking might relate to the reservation policies.
Wait, the crossover topics say the upcoming events document includes whether a ticket is needed. But the user is asking if booking a ticket is required. The reservations document might have info on how to book those tickets or the policies around it. Since the user is asking about events needing a booking, the next node might need to reference both documents: upcoming events for event details and reservations for how to book.
According to the guidelines, if the query involves whether a reservation is required, the reservations document must be included. Even though the core info is in the upcoming events, the reservations doc provides context on booking procedures. So, include it.
</think>
{
"reasoning": "The user's query asks about upcoming events requiring ticket booking. While event details are covered in the *upcoming events document*, the mention of 'booking a ticket' directly implicates reservation-related actions (how bookings are made, policies for events requiring reservations). The reservations document contains critical context about booking procedures and policies, which the next node will need to confirm whether reservations are required for specific events and how to act on that requirement.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I book a reservation for an event in advance?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break down the user's query: "Can I book a reservation for an event in advance?" The key terms here are "book a reservation" and "event in advance."
First, the main topic is about making a reservation for an event. The reservations document contains information on how to make reservations, including policies and procedures. Even though the event itself might be covered in the upcoming events document, the user is specifically asking about booking a reservation for it.
Checking the crossover topics, the upcoming events document does include event details like dates and tickets, but the act of booking a reservation is handled by the reservations document. The query isn't just about the event's existence but about the reservation process for it. Since the user mentions "book a reservation," this directly ties into the actions the reservations document supports, such as making reservations and checking policies related to events.
Additionally, the guidelines mention that if the query involves reservation actions or whether a reservation is needed, the reservations document must be included. Even if the event details are elsewhere, the core of the query is about the reservation process, which is covered here. Therefore, including the reservations document is necessary to provide the required context for the next step in handling the reservation request.
</think>
{
"reasoning": "The query directly asks about booking a reservation for an event, which falls under the reservations document's scope of handling reservations, policies, and procedures. The document provides details on how to make reservations and includes context about event-related booking requirements, even if event specifics are covered in other documents. The 'book a reservation' intent explicitly triggers the need for this document.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Is there a way to reserve spots for upcoming events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Alright, let's tackle this query: "Is there a way to reserve spots for upcoming events?"
First, I need to check if the reservations document is relevant. The user is asking about reserving spots, specifically for upcoming events. The main focus here is on reservations, even though it's tied to events.
Looking at the reservations document contents, it includes info on how to make reservations, check them, and policies related to reservations. Even though upcoming events are covered in their own document, the act of reserving spots would involve the reservations process, which is handled in the reservations document.
The crossover topics mention that events are in the upcoming events document. However, the query isn't just about event details but reserving spots for them. Since the action of reserving (making a reservation) is part of the reservations document's scope, even if the event details are elsewhere, the reservations document is needed here.
The guidelines state that if the query involves reservation actions or policies, the document should be included. Even though the event itself is in another doc, the reservation process is key here. The next node would need the reservations doc to explain how to reserve spots for any event, ensuring policies like minimum spends or time limits are considered.
So, the decision is to include the reservations document because the core of the query is about making a reservation, even if it's for an event covered elsewhere.
</think>
{
"reasoning": "The query explicitly asks about reserving spots for upcoming events, which directly involves reservation/booking intent. While event details are covered in the 'upcoming events document', the mechanism to reserve spots (policies, processes, or actions like 'how to make a reservation') falls under the reservations document. Additionally, the next node would require reservations context to confirm whether reservations are possible for events, how they are handled (e.g., group policies), and how to execute the reservation action.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are tickets available for booking for any events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's figure out if the reservations document should be included for the query: "Are tickets available for booking for any events?"
First, the user is asking about ticket availability for events. From the crossover topics, the upcoming events document covers event details, including whether tickets are needed. The reservations document doesn't handle event tickets; it's about reservation policies, seating, etc.
But according to the guidelines, if the query involves booking intent or if the next node needs reservation context (even indirectly), include the reservations document. Here, "booking for any events" might imply needing a reservation for attending, especially if events require reservations. The next node might check if reservations (which could be tied to tickets) are available, thus needing the reservations document's info on how bookings are handled. Even though the events document has ticket info, the reservation policies might affect ticket availability. So, include reservations.
</think>
{
"reasoning": "The query asks about ticket availability for events, which primarily relates to the upcoming events document. However, the term 'booking' signals a reservation-related intent. The reservations document is needed to provide context on reservation policies (e.g., whether events require reservations, how bookings are managed) to support the next node in addressing both ticket availability and booking processes.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
How do I book for your next event?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's tackle this query. The user is asking, "How do I book for your next event?" First, I need to determine if the reservations document is relevant here. The query is about booking for an event, which implies a reservation. The upcoming events document handles event details, but booking actions are covered in the reservations document.
Looking at the crossover topics, the reservations document includes info on how to make reservations, which the user is asking about. Even though the event details are in another document, the action of booking is part of reservations. The guidelines mention including the document if there's reservation intent. Since the user wants to book, the reservations doc must be included to provide the process details, even if event info is elsewhere. Decision: include.
</think>
{
"reasoning": "The query 'How do I book for your next event?' directly signals an intent to take action to reserve or book an event. While information about the event itself would come from the upcoming events document, the actual process of booking (e.g., steps, policies, or reservation actions) is covered in the reservations document. The reservations document contains information on 'how to take action [...] to make a reservation,' including policies and procedures that may apply to event bookings. Including this document ensures the next node has context about reservation requirements, minimum spends, or other policies that could influence the booking process, even if event-specific details are sourced elsewhere.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any upcoming ticketed events I should book?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's look at the query: "Are there any upcoming ticketed events I should book?" The user is asking about upcoming ticketed events and whether they should book them.
First, I need to check if the reservations document is relevant here. The reservations document contains info on reservation policies, how to make reservations, cancellation policies, etc. The query is about ticketed events, which would normally fall under the upcoming events document. The events document has details on event dates, times, ticket requirements, and event descriptions.
But the user uses the word "book," which might indicate an intent to make a reservation. Even if the events are ticketed, the act of booking could relate to reserving a spot or a table for the event. The guidelines mention that if there's a booking intent, the reservations document should be included to provide context, even if the main answer comes from another document.
The crossover topics for the upcoming events document don't cover reservation policies. However, the user's mention of "book" suggests they might need to know if a reservation is required or how to make one for the event. The reservations document would have info on how to make reservations, which the next node might need to reference when discussing booking the event tickets.
So even though the main answer about events is in the upcoming events doc, the reservations doc is needed because the user is talking about booking. Therefore, include the reservations document.
</think>
{
"reasoning": "The query mentions 'book' in relation to upcoming ticketed events, signaling booking/reservation intent. While event details would come from the upcoming events document, the reservations document is required to provide context about reservation policies, procedures, or whether reservations are needed for events. This ensures the next node has full information to address both event availability and booking logistics.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you accept event reservations?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's tackle this query: "Do you accept event reservations?" The user is asking if the venue accepts reservations for events. I need to check if the reservations document is relevant here.
First, I look at the reservations document's contents. It includes info on reservation policies, how large groups are handled, and how to make reservations. The user's question is specifically about event reservations, which would fall under the venue's reservation policies. The reservations document covers whether they accept reservations for events, especially since events might require special arrangements mentioned in the policies like minimum spends or group handling.
Now, checking crossover topics. The venue information document includes things like location and facilities but not reservation policies. The menu document is about food items, which isn't relevant here. The upcoming events document lists event details but not whether reservations are needed or accepted for them.
The guidelines say that if the query involves reservations, even if the core is about events, we include the reservations document. Since the user is explicitly asking about accepting reservations for events, the reservations document is necessary to confirm if such reservations are possible and under what policies. Therefore, including it makes sense because the next node needs this info to answer correctly.
</think>
{
"reasoning": "The query directly asks about accepting event reservations, which falls under the venue's reservation policies. The reservations document contains information on reservation policies, handling of large groups/bookings, and how to take action on reservations. While events might be covered in the upcoming events document, the specific mention of reservations in the query triggers the need for the reservations document to address policies and procedures around event reservations. Additionally, the next node may require the reservations document to verify if reservations are possible for events and under what conditions, even if event details are in another document.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I pre-book an event reservation?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let me process this query. The user is asking, "Can I pre-book an event reservation?" The key terms here are "pre-book" and "event reservation." I need to determine if the reservations document is relevant.
First, checking the reservations document contents: it includes info on making reservations, policies, and handling groups/large bookings. The query is about booking an event, which likely involves reservations.
Next, looking at crossover topics. The upcoming events document covers event details, tickets, and event-specific policies. However, the user is asking about booking/reserving an event, which implies a reservation action. Even if the event details are in another document, the act of reserving would require the reservations document's policies and procedures.
Guidelines say to include reservations doc if there's any mention of reservations/booking, even if part of the answer is elsewhere. Since the query is about making a reservation for an event, the reservations document is needed for policies on how to make the reservation, minimum spends, cancellation policies, etc. Even though event details might be in another doc, the reservation aspect is covered here.
Also, the next node might need the reservations doc to check if event reservations are possible and their terms. So including it provides necessary context. Therefore, the decision is to include the reservations document.
</think>
{
"reasoning": "The query directly asks about pre-booking an event reservation, which explicitly involves reservation/booking intent. While event details might be covered in the upcoming events document, the reservations document is required to address policies and procedures for making reservations (e.g., how to act, cancellation rules, group handling). Additionally, even if the core event information resides elsewhere, the reservations document provides critical context for validating reservation feasibility and requirements, as per guidelines.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any VIP events that need reservations?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's look at the query: "Are there any VIP events that need reservations?" The user is asking about VIP events and whether reservations are required for them. First, I need to check which document contains information about events. The Upcoming Events Document includes details about special events, including whether tickets are needed and event-specific policies. However, the query specifically mentions "need reservations," which relates to whether a reservation is necessary.
The Reservations Document includes information on policies regarding reservations, including for events. Even though the main event details are in the Upcoming Events Document, the part about needing reservations would be covered in the Reservations Document. Also, the guidelines state that if the query involves whether a reservation is required, even if the core is about events, the Reservations Document should be included to provide context on policies. So even though the event details are elsewhere, the reservation requirement check means including Reservations.
</think>
{
"reasoning": "The query asks whether VIP events require reservations. While the Upcoming Events Document contains details about events themselves, the need for reservations directly ties into reservation policies. The Reservations Document includes information about scenarios where reservations are required (e.g., for reserved areas, group bookings) and cancellation policies, which could apply to event-specific reservations. Including this document ensures context about reservation requirements is available, even if event details are handled separately.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I reserve a ticket for any special events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let me break this down. The user is asking, "Can I reserve a ticket for any special events?" So first, I need to determine if the reservations document is relevant here.
The query mentions reserving tickets for special events. The reservations document includes info on how to make reservations and policies around them. The upcoming events document would handle details about the events themselves, like dates and ticket requirements. However, the user is specifically asking about reserving tickets, which implies a booking intent. Even though event details are in another document, the act of reserving a ticket might involve the reservation policies or procedures outlined in the reservations document.
The guidelines say that if the query involves reservation actions or whether reservations are needed, the reservations document should be included. Here, the user is asking about reserving tickets, which is a booking action. The next node might need the reservations document to provide info on how to make a reservation, even if event specifics are elsewhere. So, including the reservations document would give necessary context for the reservation process related to special events.
</think>
{
"reasoning": "The query asks about reserving tickets for special events. While event details are covered in the upcoming events document, the act of reserving tickets signals booking intent. The reservations document contains information on how to make reservations and policies surrounding bookings, which is necessary to provide context for handling ticket reservations (even if the event details themselves are elsewhere). The next node may need this document to address reservation procedures or policies tied to special events.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
How can I make a booking for your next event?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "How can I make a booking for your next event?" First, I need to determine which documents are relevant here. The main topics here are making a booking and referencing an event.
The reservations document contains info on how to make reservations, including actions like making or checking reservations. The query explicitly mentions "make a booking," which directly relates to the reservations document's content on taking action to reserve. Even though the user mentions "next event," which might be covered in the upcoming events document, the core of the query is about the booking process.
Now, checking the crossover topics: the upcoming events document includes event details but not the reservation process. The reservations document is needed here because even if the event info is in another document, the user wants to book it, so the reservations document's procedures are essential. The guidelines state that if there's any reservation intent, include the document. Plus, the next node might need reservation policies to confirm if bookings are possible for events and the steps involved. Thus, including the reservations document is necessary to answer how to make the booking, even if event specifics are elsewhere.
</think>
{
"reasoning": "The query asks about making a booking for an event, which explicitly involves reservation intent ('make a booking'). While the 'next event' might fall under the upcoming events document, the core action requested (booking/reserving) is directly addressed by the reservations document. The reservations document includes information on how to take action to make reservations, which is critical here. Additionally, the next node would need the reservations document to verify policies or steps required for event-related bookings, even if event specifics are handled elsewhere.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do I need a reservation for the next scheduled event?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "Do I need a reservation for the next scheduled event?" The key part here is "reservation for the next scheduled event." The query is specifically about whether a reservation is required for an event.
First, I need to check if the reservations document covers information about reservations for events. According to the system message, the reservations document includes policies like walk-in seating, minimum spends, time limits, cancellation policies, and handling groups. It also mentions how to make or check reservations. However, details about events themselves (like dates, tickets, event-specific rules) are in the upcoming events document.
But the user isn't asking about the event details; they're asking if a reservation is needed. The reservations document includes policies on whether reservations are required, especially for events. Even though the event details are in another document, the need for a reservation relates to reservation policies.
The guidelines state that if the query asks whether a reservation is needed, the reservations document must be included. Even if the event details are elsewhere, the reservation requirement is a policy covered by the reservations document. Additionally, the next node might need the reservation info to confirm policies around event bookings. So, including the reservations document here provides necessary context about needing reservations, even if the event specifics are in another document.
</think>
{
"reasoning": "The query asks whether a reservation is needed for an upcoming event. While event-specific details (e.g., ticket requirements) are covered in the upcoming events document, the need for a reservation directly relates to reservation policies, which are explicitly within the reservations document. The document includes rules about reservations for reserved areas/events, time limits, and how bookings are handled, which are critical to answering this query. Additionally, even though the event itself is described in another document, the reservations document must be included to verify policies around reservation requirements, aligning with the guideline that queries involving 'whether a reservation is needed' mandate inclusion.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any events that require online booking?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "Are there any events that require online booking?"
First, I need to figure out which document this query relates to. The main topics here are "events" and "online booking." The Upcoming Events document contains information about events, including whether tickets are needed. The Reservations document deals with bookings and reservation policies.
The query is about events that require online booking. Even though the events themselves are covered in the Upcoming Events document, the part about whether booking is required ties into reservation policies. The Reservations document includes info on how bookings are handled, like whether reservations are necessary for certain areas or events. Since the user is asking if an event requires a reservation (online booking), the Reservations document would have the policies that determine that. Even if the event details are elsewhere, the requirement to book is part of the reservation policies. Therefore, including the Reservations document is necessary to provide context on whether bookings are needed for events, which the next node can cross-reference with the Upcoming Events info.
</think>
{
"reasoning": "The query asks whether events require online booking. While the Upcoming Events document contains event details, the requirement for booking/reservation directly relates to reservation policies. The reservations document includes information on whether reservations are needed for certain areas or events, cancellation policies, and procedures for making bookings. Including the reservations document provides context on reservation requirements, which is essential to answer whether events need online booking, even if event specifics are in another document.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do I need to book in advance for your events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's take a look at the user's query: "Do I need to book in advance for your events?" The user is asking whether booking in advance is necessary for events at the venue.
First, I need to check if this falls under the reservations document. The reservations document includes information on policies like whether reservations are required, cancellation policies, and how bookings are handled. The query is specifically about needing to book for events, which directly relates to reservation policies.
Now, checking the crossover topics. The upcoming events document contains event details, including whether tickets are needed. However, the question isn't just about event existence or tickets; it's about the necessity of booking. The reservations document covers policies around reservations, including if they're required for certain areas or events. Even if events have their own ticket info, the need to book (reserve) a spot at the venue for the event would depend on the venue's reservation policies, which are in the reservations document.
The guidelines mention that if the query is about whether a reservation is required, the reservations document must be included. Even if events might have their own ticket requirements, the act of booking a reservation (as opposed to purchasing a ticket) is covered here. The next node might need the reservations document to confirm if events require a reservation in addition to any tickets. Therefore, including the reservations document is necessary to provide the context on reservation requirements.
</think>
{
"reasoning": "The query asks whether booking in advance is required for events, which directly relates to reservation policies. While event-specific details (e.g., tickets) may reside in the upcoming events document, the question of whether reservations are *required* falls under the reservations document's scope. This document includes policies like reservation requirements, time limits, and procedures, which are needed to address the 'need to book' aspect. Additionally, even if event tickets are discussed elsewhere, the reservations document provides context on whether securing a reservation (separate from tickets) is necessary, ensuring the next node can verify policies.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I reserve seats for any events here?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "Can I reserve seats for any events here?" The task is to decide if the reservations document should be included.
First, I need to check the query's main focus. The user is specifically asking about reserving seats for events. The reservations document contains info on reservation policies, how to make reservations, and details about seating layouts. Even though there's an events document, the mention of reserving seats directly ties into the reservations document's content. The events document might list event details but not the reservation process itself. Since the user is asking about the action of reserving seats, which involves policies and procedures covered in the reservations document, it should be included. Also, the guidelines mention including the document if there's any reservation intent, even if part of the query relates to another document. Therefore, include reservations here.
</think>
{
"reasoning": "The query directly asks about reserving seats for events, which involves the reservation policies and procedures covered in the reservations document. While events are detailed in another document, the act of reserving seats (including policies, availability, and processes) falls under the scope of the reservations document. Additionally, the user's explicit mention of reserving triggers the need for the reservations document to provide context on how reservations work, even if event details are handled elsewhere.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are bookings required for any events happening soon?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Alright, let's tackle this query: "Are bookings required for any events happening soon?"
First, I need to determine if the reservations document is relevant here. The user is asking whether bookings are needed for upcoming events. The key part here is "bookings required," which directly relates to reservation policies.
Looking at the crossover topics, the Upcoming Events document contains info about events, including whether tickets are needed. However, the user specifically mentions "bookings," which might refer to reservations rather than tickets. The Reservations document includes policies on whether reservations are necessary, especially for events.
The guidelines mention that any query asking if a reservation is required, even if it's about events, should include the Reservations document. This is because the next node might need reservation policies to confirm if bookings are mandatory for those events. Even if the event details are in another document, the reservation requirement check relies on the Reservations document.
Therefore, including the Reservations document provides the necessary context about reservation policies for the upcoming events, making it relevant here.
</think>
{
"reasoning": "The query asks whether bookings are required for upcoming events. While the Upcoming Events document contains details about events, the question directly relates to reservation requirements. The Reservations document includes policies on whether reservations are needed (e.g., for reserved areas, group handling, or event-specific rules). Even though event details are in another document, the reservations document is necessary to determine if bookings are mandatory for those events, aligning with guidelines to include it when reservation intent is signaled.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any exclusive events I need to book?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Alright, let's tackle this query. The user is asking, "Are there any exclusive events I need to book?" First, I need to determine if the reservations document is relevant here.
The key parts of the query are "exclusive events" and "need to book." The Upcoming Events Document would handle details about the events themselves, like dates, descriptions, and whether tickets are needed. However, the user is specifically asking if booking is required, which relates to reservation policies.
The Reservations Document includes info on policies like how to make reservations and whether reservations are necessary for certain areas or events. Even though the event details are in another document, the act of booking or needing a reservation falls under the Reservations Document's purview.
The guidelines mention that if the query involves whether a reservation is required, the Reservations Document should be included. Since the user is asking about the need to book events, the next node will need the Reservations Document to confirm policies around bookings for events. Even if the event details are elsewhere, the reservation requirement context is crucial here. So, include the document.
</think>
{
"reasoning": "The query asks about the need to book exclusive events, which directly relates to reservation policies and whether reservations are required for specific events. While event details are covered in the Upcoming Events Document, the mention of 'booking' indicates a need to reference reservation policies, procedures, or requirements. The Reservations Document provides context on whether reservations are necessary, how to make them, and any policies tied to event bookings, which is critical for the next node to verify even if event specifics are sourced elsewhere.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you have an event that needs a prior booking?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's analyze the query: "Do you have an event that needs a prior booking?" The user is asking about events that require reservations. The key terms here are "event" and "prior booking."
First, I check the crossover topics. The Upcoming Events document contains info on events, including whether tickets are needed. However, the query isn't just about the existence of events but specifically about events requiring a prior booking (reservation). The reservations document includes policies about reservations, including how large groups or bookings are handled and whether reservations are necessary.
Even though events are covered in their own document, the mention of "prior booking" ties directly to reservation policies. The next node might need the reservations document to confirm if any events indeed require reservations and what those policies are. Therefore, including the reservations document provides necessary context about reservation requirements, even if the event details are elsewhere.
</think>
{
"reasoning": "The query asks about events requiring a prior booking, which explicitly ties to reservation policies (e.g., whether reservations are needed for specific events). The reservations document contains information about reservation requirements, cancellation policies, and procedures for making reservations. While events are covered in the upcoming events document, the mention of 'prior booking' directly signals a need to reference reservation policies to determine if reservations are mandatory for events. This aligns with the guideline that any query involving reservation requirements, even if events are mentioned, necessitates including the reservations document for context.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
What events can I book right now?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's tackle this query. The user is asking, "What events can I book right now?" The first thing I notice is the word "book." That immediately makes me think about reservations or bookings. The main document in question here is the reservations document. I need to check if the query relates to the contents of that document.
The reservations document includes information on making reservations, checking them, and policies related to bookings. The upcoming events document, which is separate, lists events and their details. However, the user is not just asking about events but specifically about booking them. Even though the events themselves are in the upcoming events document, the act of booking implies that reservation policies or procedures might be necessary.
Looking at the crossover topics, the upcoming events document covers event details and whether tickets are needed. But the user's use of "book" suggests they might need to make a reservation for the event. The guidelines mention that if the query involves reservation policies or whether a reservation is needed for an event, the reservations document should be included.
Even if the answer about available events is in another document, the next node might need the reservations document to address booking requirements, like how to make a reservation for an event or if there are specific policies for event bookings. Therefore, including the reservations document provides necessary context for the next steps.
</think>
{
"reasoning": "The query includes the term 'book' which signals reservation intent. While event details are in the upcoming events document, the reservations document is required to address booking-related policies, procedures, or context (e.g., how reservations interact with events, minimum spends for reserved event areas). This aligns with the guideline to include reservations when booking intent is present, even if event details reside elsewhere.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you have an online booking system for events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "Do you have an online booking system for events?"
First, I need to check if this relates to the reservations document. The reservations document includes info on how to make reservations, check them, and policies around that. The query is specifically about an online booking system, which is part of making a reservation. The reservations document details how actions can be taken on behalf of the customer, like making a reservation. So, this fits under the "how to take action" part of the reservations doc.
Next, checking crossover topics. Venue info covers things like location, payment methods, etc., which aren't relevant here. The menu document is about products and last orders, which isn't the case. Upcoming events would handle event specifics, but the question isn't about event details; it's about booking methods.
The guidelines mention including the reservations doc if the query involves reservations or booking, even if the next node needs it for context. Since the user is asking about online booking systems, which is directly related to making reservations, the reservations document is necessary here. Even if the exact answer isn't there, the next node might need the info on how reservations are handled to respond accurately. Therefore, include the reservations document.
</think>
{
"reasoning": "The query specifically asks about an online booking system for events, which directly relates to the 'how to take action' section of the reservations document. This document contains information on how reservations are made (including potential online systems) and procedures for checking or managing bookings. While the exact term 'online booking system' may not be explicitly listed, the document's coverage of reservation processes and actions aligns with the user's request. Additionally, the next node would require the reservations document to verify details about booking methods, even if the answer involves confirming the existence of an online system.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you offer advance bookings for events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's analyze this query. The user is asking, "Do you offer advance bookings for events?" The key term here is "advance bookings," which directly relates to reservations. The reservations document includes information on how to make reservations and the policies around them. Even though events are mentioned, the core of the question is about booking procedures, which fall under the reservations document's purview. The crossover topics in other documents don't cover booking procedures, so the reservations document is necessary here.
</think>
{
"reasoning": "The query asks about advance bookings for events, which directly relates to reservation policies and procedures. While the term 'events' might overlap with the upcoming events document, the core of the query focuses on booking/reservation intent. The reservations document includes information on how to make reservations, check reservations, and policies like group handling—all necessary to confirm whether advance bookings are offered and under what terms. Even if event-specific details are in another document, the reservation process itself is covered in the reservations document, making it essential for context.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
How far in advance should I reserve for an event?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Alright, let's break this down. The user's query is asking how far in advance they should reserve for an event. First, I need to determine which document this falls under. The main focus here is on reservation timing, which directly relates to the reservation policies mentioned in the reservations document, like time limits and how groups are handled. The other documents don't cover reservation timing. Even though "event" might make me think of the upcoming events document, that's more about event details rather than reservation lead times. Also, the guidelines mention that any query involving reservation policies or needing context for reservations should include the reservations document. Since this is about when to book, the reservations document is necessary here.
</think>
{
"reasoning": "The query specifically asks about reservation timing ('how far in advance'), which falls under the reservation policies covered in the reservations document (e.g., time limits, handling of large bookings). While the query mentions 'an event,' the core focus is on reservation logistics rather than event-specific details like dates, tickets, or descriptions (covered in the upcoming events document). The reservations document is necessary to provide context on advance booking requirements and policies, aligning with the guideline that reservation-related intent triggers inclusion.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any ticketed events open for booking?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break down the user's query: "Are there any ticketed events open for booking?" The main focus here is on ticketed events and their availability for booking. Now, looking at the reservations document, it primarily contains information about reservation policies, seating arrangements, cancellation policies, and how to make or check reservations. The upcoming events document, on the other hand, includes details about events, including whether tickets are needed.
The query is specifically asking about ticketed events and their booking status. The upcoming events document should handle event details, including ticket requirements and event dates. However, the mention of "open for booking" could imply that making a reservation or booking is necessary for these events. Since the reservations document includes information on how to take action to make a reservation, it might be needed here. Even though the events themselves are covered in the upcoming events document, the act of booking or reserving tickets could require the context from the reservations document to understand the process, policies, or availability. Therefore, including the reservations document provides necessary context for the next node to accurately address both the event details and the booking process.
</think>
{
"reasoning": "The query asks about ticketed events 'open for booking,' which implies a need to check event availability and reservation/booking procedures. While event details are covered in the 'upcoming events' document, the mention of 'booking' signals reservation intent. The reservations document contains critical context about how to check or make reservations, which may apply to ticketed events (e.g., policies for reserving event spaces or tickets). Including the reservations document ensures the next node can verify if bookings are required or supported for these events, even if the core answer resides in the upcoming events document.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any must-book events coming up?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, so the user is asking, "Are there any must-book events coming up?" Let me break this down.
First, the query is about upcoming events that require booking. The main topic here is events, which would typically fall under the Upcoming Events Document. That document contains details about special events, their dates, times, whether tickets are needed, etc. So the answer to which events are coming up would be there.
But the user specifically uses "must-book," implying that reservations might be necessary for these events. Now, even though the events themselves are covered in another document, the part about whether booking is required or the policies around it could be in the Reservations Document. For example, the Reservations Document might have info on whether certain events require reservations, any minimum spends, cancellation policies, or how to book them.
The guidelines say that if the query involves whether a reservation is needed, the Reservations Document should be included. Here, the user is asking about events that you "must-book," so even though the events are in another document, the requirement to book them might be covered in reservations. Additionally, the next node might need to check if these events have associated reservation policies. For example, an event might be listed in the Upcoming Events Document, but the Reservations Document would have info on how to reserve a spot for it, any special conditions, etc.
Also, the reasoning example mentioned that if the user signals booking intent, even if the core is elsewhere, the Reservations Document is included. Here, "must-book" clearly indicates a reservation is needed, so including Reservations makes sense to provide context on how to book those events. Without that, the answer might list events but not address the booking aspect, which is key here.
So, even though the main event info is elsewhere, the booking component ties into Reservations. Hence, include the Reservations Document.
</think>
{
"reasoning": "The query asks about 'must-book events', which signals reservation intent. While event details reside in the Upcoming Events Document, the 'must-book' qualifier implies the need to reference reservation policies (e.g., whether bookings are mandatory, how to reserve for events). The reservations document contains critical context about reservation requirements, procedures, and policies that would inform the answer, even if event specifics are covered elsewhere. Including it ensures the next node can address both the event availability *and* the booking requirements.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you require a reservation for any weekend events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Alright, let's break this down. The user is asking, "Do you require a reservation for any weekend events?" The first thing I need to determine is whether the reservations document is relevant here.
First, the query mentions "require a reservation," which directly relates to reservation policies. The reservations document includes information on when reservations are necessary, such as policies for walk-ins versus reservations, which is exactly what the user is asking about. Even though the question is about weekend events, the core of it is whether a reservation is needed, which falls under the reservation policies covered in the reservations document.
Next, looking at the crossover topics, the upcoming events document might have info about events, but the user's question isn't about the events themselves—it's about the need for reservations for those events. The reservations document would outline if reservations are required for certain events, especially weekend ones. Even if the events document lists the events, the policy on whether reservations are mandatory would be in the reservations document or linked through it.
The guidelines mention that if the query asks whether a reservation is required, the reservations document must be included. This query is explicitly about needing a reservation, so including the reservations document is necessary. The next node might need to check both the events and reservations docs, but even if not, the reservations doc provides the policies on reservations for events.
Therefore, despite the mention of events, the key factor here is the need for a reservation, which is covered in the reservations document. So, the decision is to include it.
</think>
{
"reasoning": "The query asks whether reservations are required for weekend events, directly involving the need for reservations. The reservations document contains policies on whether reservations are mandatory (e.g., for events) and how they are handled. While events are covered in the 'upcoming events' document, the question specifically ties reservations to events, making the reservations document relevant to address reservation requirements and policies. The next node may also need this document to verify if reservations for events fall under standard policies or specific event rules.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I reserve a slot for any events this month?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break down the user's query: "Can I reserve a slot for any events this month?" The user is clearly asking about making a reservation for events. First, I need to check if the reservations document is relevant here.
The reservations document contains info on how to make reservations, policies, and procedures. The user's query specifically uses the word "reserve," indicating intent to book something. Even though events are covered in the upcoming events document, the act of reserving a slot relates directly to the reservations process.
Looking at the crossover topics, the upcoming events document includes event details but not the reservation process. The user isn't just asking about event details; they want to reserve a slot. According to the guidelines, if the query involves reservations or booking intent, the reservations document should be included.
Additionally, the next node might need the reservations document to check policies like how to make a reservation, availability, or any requirements for event bookings. Even though event specifics are in another document, the reservation action ties back to the reservations document. Therefore, including it provides necessary context for processing the reservation request.
</think>
{
"reasoning": "The query directly asks about reserving a slot for events, which signals a booking intent. While event details are covered in the upcoming events document, the act of reserving a slot (even for events) falls under the reservations document's scope, as it involves reservation policies, procedures, or actions like making/checking reservations. The reservations document is needed to address the core action of reserving and to provide context for policies that might apply to event reservations.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do I need to pre-book for any live events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's tackle this query: "Do I need to pre-book for any live events?"
First, I need to determine if the reservations document is relevant here. The user is asking about pre-booking for live events. The key words here are "pre-book" and "live events".
The crossover topics mention that upcoming events are covered in their own document, which includes info like event dates, tickets, etc. But the user isn't just asking about the events themselves; they're specifically asking if pre-booking is necessary.
Now, looking at the reservations document's contents, it includes policies about reservations, whether they're needed, how to make them, and handling groups. Even though the events are detailed in another document, the question of whether a reservation (pre-booking) is required would likely involve the reservation policies. Also, the guidelines state that if the query is about whether a reservation is needed, even if the core is elsewhere (like events), the reservations document must be included.
The upcoming events document might mention if an event requires a ticket, but "pre-book" implies reservation policies, which are in the reservations doc. Plus, the next node might need reservation info to cross-check if events require bookings. So, include the reservations document here.
</think>
{
"reasoning": "The query asks whether pre-booking is required for live events. While live events are covered in the upcoming events document, the core of the question hinges on reservation requirements, which directly relates to reservation policies. The reservations document contains details on reservation procedures, policies for events (e.g., time limits, cancellation rules, group handling), and whether reservations are necessary for certain activities. Even though event-specific details exist elsewhere, the need for pre-booking falls under reservation policies, necessitating inclusion of the reservations document for context.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I book multiple tickets for an upcoming event?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's analyze the query step by step. The user is asking, "Can I book multiple tickets for an upcoming event?" The key terms here are "book multiple tickets" and "upcoming event."
First, I need to check if the query relates to the reservations document. The reservations document contains information on making reservations, policies for groups, and handling large bookings. Booking multiple tickets likely involves group reservations, which are covered here.
Next, looking at the crossover topics. The upcoming events document includes event details, ticket requirements, and event-specific policies. However, the user is asking about booking multiple tickets, which is about the reservation process rather than the event details themselves.
The guidelines mention that if the query involves booking or reservation actions, even if the event is part of the question, the reservations document should be included. Since the user wants to book multiple tickets (which implies a group reservation), the reservations document is necessary to address policies on group bookings, minimum spends, or seating arrangements for larger parties.
Additionally, the next node might need the reservations document to confirm if group bookings are allowed and any associated policies, ensuring the answer is accurate. Even though the event details are in another document, the act of booking multiple tickets directly relates to reservation procedures, making the reservations document relevant here.
</think>
{
"reasoning": "The query asks about booking multiple tickets for an upcoming event. While event details reside in the 'upcoming events' document, the act of *booking multiple tickets* directly signals reservation intent and involves group booking policies (e.g., minimum spends, seating arrangements for large groups). The reservations document is needed to confirm policies for group reservations and provide context for the booking process, even if event-specific ticket details are handled elsewhere.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are event reservations refundable?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's tackle this query: "Are event reservations refundable?"
First, I need to check if this question falls under the reservations document. The user is asking about refunds for event reservations. The reservations document includes cancellation policies, which cover refunds for no-shows or late arrivals. Since the query is about refunds related to reservations, the answer should be in the reservations document.
Now, looking at the crossover topics, the venue information document deals with service charges and payment methods, but not refund policies for reservations. The other documents like menu and upcoming events don't cover reservation cancellations either. Since the question is specifically about reservations and their refund policies, the reservations document is needed here.
Also, even if the answer isn't directly in the document, the next node might need the cancellation policies from reservations to provide context. So including it makes sense. There's a mention of booking intent in the query, which aligns with the guideline to include reservations when there's a booking-related intent.
Therefore, the reservations document should be included.
</think>
{
"reasoning": "The query directly asks about refund policies for event reservations, which falls under the cancellation policies covered in the reservations document. While refunds might also relate to payment methods (venue information document), the core of the query is tied to reservation-specific cancellation rules. The reservations document contains explicit details about cancellation policies, including refunds for late arrivals or no-shows, making it essential for answering this query. Additionally, the user's mention of 'event reservations' signals booking intent, further necessitating inclusion of the reservations document to provide context for the next node.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any events that have limited booking slots?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Alright, let's tackle this query: "Are there any events that have limited booking slots?"
First, I need to determine if the reservations document is relevant. The query is about events with limited booking slots. The upcoming events document would have details on events, but the mention of "limited booking slots" implies that there might be a need to check reservation availability or policies.
Looking at the reservations document's contents, it includes info on how groups and large bookings are handled, time limits, and cancellation policies. These could relate to booking slots. However, the events document details if tickets are needed, which might include booking info.
But the guidelines say to include the reservations doc if the query involves whether reservations are required or booking-related context, even if the core is elsewhere. Since "limited booking slots" suggests checking reservation availability or capacity, the next node might need reservation policies (like max group size) to answer accurately. Even if events are in another doc, the booking aspect ties back to reservations. So including reservations doc here provides necessary context on booking limitations.
</think>
{
"reasoning": "The query asks about events with 'limited booking slots,' which implies a need to check reservation availability or policies tied to events. While event details are in the upcoming events document, the mention of booking slots relates to reservation capacities and how bookings are managed. The reservations document includes policies on handling groups, time limits, and cancellation rules, which are relevant to determining if booking slots are limited. Additionally, the next node may require the reservations document to contextualize whether event bookings have restrictions (e.g., minimum spends, group size limits) even if the events themselves are listed elsewhere.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I book a table for any upcoming events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let me think through this. The user's query is "Can I book a table for any upcoming events?"
First, I need to determine if the reservations document is relevant here. The query mentions "book a table," which directly relates to making a reservation. The reservations document contains information on how to make reservations and check them, as well as policies that might apply.
Now, looking at the crossover topics. The upcoming events document handles details about events themselves—dates, times, tickets, etc. But the user is asking about booking a table for those events. Even though the events info is in a different document, the actual act of booking a table falls under reservations.
The guidelines mention that even if the core of the query involves another document (like upcoming events), if there's a mention of booking or reservation, the reservations document should be included. The next node might need to check if reservations are possible for events, and the reservations document provides the necessary policies and procedures.
So, even though the events are in another document, the booking aspect means the reservations document is needed. Therefore, include it.
</think>
{
"reasoning": "The query asks about booking a table for upcoming events. While the specifics of upcoming events are covered in a separate document, the act of 'booking a table' directly relates to reservation policies, procedures, and seating layouts described in the reservations document. Additionally, the query implies a need to verify whether reservations are required or possible for events, which requires context from the reservations document to confirm policies like minimum spends, time limits, or group handling. Even though event details reside elsewhere, the reservation intent triggers inclusion of this document to support actionable steps (e.g., making a reservation) and policy checks.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Is it possible to reserve a space for an event?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "Is it possible to reserve a space for an event?" The main task here is to determine if the reservations document should be included to answer this query.
First, looking at the query: they're specifically asking about reserving a space for an event. The reservations document includes information on reservation policies, how groups and large bookings are handled, and details on seating layouts. The ability to reserve a space, especially for events, likely involves group bookings or specific areas of the venue, which are covered in the reservations document.
Next, checking the crossover topics. The venue information document covers location, facilities, payment methods, etc., but not reservation procedures. The menu document is irrelevant here. The upcoming events document talks about event details but not the reservation process for hosting an event. Since the query is about reserving space, not the event itself, the other documents don't apply.
Guidelines mention that any query involving reservations or bookings requires including the reservations document. Even if part of the answer might relate to events (which are in another document), the core of this query is about the reservation process, which is directly covered in the reservations document. Additionally, the next node might need this document to confirm policies on event reservations, minimum spends, or group handling.
Therefore, the reservations document is essential here. It directly addresses reservation possibilities and provides necessary context for the next steps.
</think>
{
"reasoning": "The query directly asks about reserving a space for an event, which falls under the scope of the reservations document. The document contains information on policies for reservations, handling of groups/large bookings, seating layouts, and procedures for making reservations—all critical to answering whether event space reservations are possible. While events themselves are covered in the upcoming events document, the act of reserving space for an event inherently involves reservation policies and procedures, which the reservations document addresses. Additionally, the next node would need this document to verify policies like minimum spends, time limits, or group size compatibility with the venue's seating layouts.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any events I can reserve right now?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's look at the user's query: "Are there any events I can reserve right now?" The key words here are "events" and "reserve." The Upcoming Events Document contains info about events, but the user is specifically asking about reserving them. The Reservations Document includes how to make reservations and policies around bookings. Even though events are covered in another document, the mention of reserving means the Reservations Document is needed for context on how to actually reserve those events. So include it.
</think>
{
"reasoning": "The query asks about reserving events, which signals booking intent. While event details are covered in the Upcoming Events document, the action of reserving an event relates to reservation policies and processes. The Reservations document is needed to provide context on how reservations are handled for events, such as checking availability, reservation procedures, or policies that might apply. Thus, including the Reservations document is necessary to address the reservation aspect of the query.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
What events do you have that require booking?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let me break this down. The user is asking, "What events do you have that require booking?" The task is to decide whether the reservations document should be included.
First, I check the reservations document contents. It covers reservation policies, how to make or check reservations, and details about seating and group handling. The upcoming events document, which is separate, lists events and whether they need tickets or bookings.
The query is about events that require booking. The upcoming events document probably has the event details, including if a ticket is needed. But the user specifically mentions "require booking," which might tie into whether a reservation is necessary. The guidelines say if the query asks if a reservation is required, include the reservations document. Even if events are in another document, needing to book could relate to the venue's reservation policies. The next node might need to cross-check if booking through reservations is needed for events, so including the reservations document provides context. So, even though events are in a different doc, the mention of booking triggers including reservations.
</think>
{
"reasoning": "The query asks about events that require booking, which implies a need to understand reservation policies for specific events. While event details are in the upcoming events document, determining whether a booking is required involves cross-referencing reservation policies (e.g., time limits, group handling, cancellation rules). The reservations document provides context on how bookings are managed, which is critical for answering whether reservations are needed for events. Since the query signals booking intent, including the reservations document ensures the next node can verify reservation requirements and procedures.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
How can I secure a booking for the next event?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "How can I secure a booking for the next event?" The key terms here are "secure a booking" and "next event."
First, I need to check if the query relates to reservations. The user is clearly talking about making a booking, which directly points to the reservations document. The reservations document includes info on how to make reservations, which is exactly what the user is asking about.
Now, looking at the crossover topics. The Upcoming Events document contains event details like dates and whether tickets are needed. But the user isn't just asking about event details; they want to book or secure a spot for it. Even though the event itself is covered in another document, the action of booking requires the reservations document.
The guidelines mention that if the query involves reservation actions, even if it's about an event, the reservations document must be included. Since the user is asking how to secure a booking, the next node would need the reservations document to provide steps on making a reservation, checking availability, or policies related to event bookings.
Even if the event details are in another document, the actual booking process is handled by the reservations document. Therefore, including it is necessary here.
</think>
{
"reasoning": "The query explicitly mentions 'secure a booking' for an event, which directly signals reservation intent. While event details might be covered in the upcoming events document, the action of booking/reserving and associated policies (e.g., minimum spends, cancellation rules) are part of the reservations document. The reservations document is needed to provide context on how bookings are processed, even if event-specific rules from other documents are also relevant.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do I have to book a pass for any of your events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "Do I have to book a pass for any of your events?" So first, I need to figure out which document this relates to. The main topics here are "book a pass" and "events."
Looking at the crossover topics, events are covered in the Upcoming Events Document, which handles event tickets and related policies. However, the query is about whether booking (a pass) is required. The Upcoming Events Document might mention if tickets are needed, but "booking a pass" could imply reservations or bookings, which are covered in the Reservations Document.
The Reservations Document includes info on reservation policies, how to make reservations, and policies about whether reservations are necessary. Even though events are in a different document, the act of booking or needing a pass ties into reservation policies. The guidelines say that if the query involves whether a reservation is required, include the Reservations Document to provide context, even if the core is about events.
So, even though the events details are elsewhere, the need to book a pass triggers the inclusion of Reservations Document to address reservation requirements and policies.
</think>
{
"reasoning": "The query asks whether a reservation ('book a pass') is required for events. While event-specific details (like ticket requirements) might be in the Upcoming Events Document, the act of 'booking a pass' directly signals reservation intent. The Reservations Document includes policies on whether reservations are necessary for certain areas or events, time limits, and procedures for making reservations. This context is critical for addressing the requirement to 'book a pass,' even if event specifics are handled elsewhere. Including the Reservations Document ensures the next node can verify reservation policies and procedures related to event attendance.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
What events require an advanced reservation?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "What events require an advanced reservation?"
First, I need to check if the query relates to reservations. The question is about events that need reservations, so directly mentions "advanced reservation." The upcoming events document would list events and their details, but the reservations document is needed to know if those events require reservations.
The crossover topics for events are in the upcoming events document, which includes info on tickets and event policies. However, whether a reservation is needed would tie into the reservation policies (like how groups are handled, minimum spends, etc.), which are in the reservations document.
The guidelines say that if a query asks if a reservation is required, include the reservations doc. Even though events are in another document, the need for reservations connects to reservation policies here. The next node might need both to answer which events need reservations, combining event info with reservation policies.
Therefore, include the reservations document because it's necessary to determine reservation requirements for events.
</think>
{
"reasoning": "The query explicitly asks about events requiring advanced reservations. While event details are covered in the Upcoming Events document, determining whether reservations are required directly ties to reservation policies (e.g., group handling, reservation time limits, cancellation rules) and actions (e.g., how to reserve). The reservations document provides context on reservation requirements, which is critical for answering the query, even if event specifics are in another document.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are your events open for booking yet?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "Are your events open for booking yet?" The first thing I need to consider is which documents are relevant here. The query mentions "booking," which immediately makes me think of reservations.
Looking at the reservations document contents, it includes information on how to make reservations and check them. The user is asking about events being open for booking. The upcoming events document probably has details about the events themselves, like dates and whether tickets are needed. But the act of booking might involve reservation policies or procedures, which are covered in the reservations document.
The guidelines mention that if the query involves booking or reservation intent, even if the core is about events, the reservations document should be included. Since the user is asking about booking events, even though events are in a different document, the next node might need the reservations document to check if booking is possible, how to do it, or any policies related to event bookings.
The crossover topics for the events document include event details but not the booking process. The reservations document handles actions like making a reservation, which applies here. So even though the events are in another document, the booking aspect requires the reservations document to provide necessary context on how bookings are handled. Therefore, the decision is to include the reservations document.
</think>
{
"reasoning": "The query asks if events are 'open for booking,' which directly signals reservation/booking intent. While event details (dates, descriptions) are in the Upcoming Events document, the ability to book/reserve for events and the mechanisms to do so (e.g., policies, procedures) are covered in the Reservations document. Including it ensures the next node has context on reservation workflows, even if events themselves are documented elsewhere.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do I need to reserve early for any special events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break down the query: "Do I need to reserve early for any special events?" The user is asking about reserving early specifically for special events.
First, I need to check if the reservations document is relevant here. The reservations document includes info on policies like whether reservations are needed, time limits, cancellation policies, and how groups are handled. The key part here is the mention of "reserve early" which directly relates to reservation policies.
Now, looking at the crossover topics. The upcoming events document contains info about special events, including whether tickets are needed, dates, etc. But the user isn't just asking about the events themselves; they're specifically asking if a reservation is required. While the events document might list the events, the need for reservations would be covered in the reservations document.
The guidelines say that if the query involves whether a reservation is required, even if events are mentioned, include the reservations doc. Since the user is asking about the necessity of reservations for special events, the policies in the reservations document would address this. Even though the events are in another document, the reservation requirement is part of the reservation policies. Plus, the next node might need the reservations doc to confirm if reservations are needed even if the events are detailed elsewhere.
Therefore, the reservations document should be included because it's about reservation requirements related to events, which falls under reservation policies.
</think>
{
"reasoning": "The query asks whether a reservation is needed early for special events. While the specifics of special events are in the Upcoming Events Document, the need to reserve (including policies on reservations for events) is covered in the Reservations Document. Even though the core topic involves events, the query explicitly ties to reservation intent, which requires the Reservations Document to confirm policies like time limits, reservation requirements, or handling of large groups during events. Additionally, the next node would need this document to validate if reservations are necessary for such events, even if event details themselves are in another document.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Is there an event I should book ASAP?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break down the user's query: "Is there an event I should book ASAP?" The user is asking about events that might require immediate booking. The first thing I need to consider is which document would contain the information about events. According to the crossover topics, the Upcoming Events Document includes details about special events, their dates, times, ticket requirements, etc. So the events themselves are covered there.
However, the user mentions "book ASAP," which implies they might need to make a reservation or secure a spot for the event. The Reservations Document includes information on how to make a reservation and check availability. Even though the main event details are in another document, the action of booking (reserving) would require the Reservations Document's policies and procedures. Additionally, the guidelines state that if the query involves reservation actions or needing a reservation, even if the core event info is elsewhere, the Reservations Document should be included to provide context on how to proceed with booking. Therefore, including it ensures the next node can address both the event details and the booking process.
</think>
{
"reasoning": "The query asks whether there's an event to 'book ASAP,' implying a need to secure a spot or reservation. While event details are in the Upcoming Events Document, the action of booking/reserving (and associated urgency) triggers the need for the Reservations Document. This document provides context on reservation procedures, policies, and seat availability checks, which are critical to answering the implied question of *how* to book the event promptly. The next node would require this document to confirm whether reservations are needed for events and guide the user on immediate booking steps.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I book an event ticket for someone else?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's look at the query: "Can I book an event ticket for someone else?" The user is asking about booking an event ticket on behalf of another person.
First, I need to check if this relates to the reservations document. The reservations document includes info on how to make reservations and policies around that. The query is about booking tickets, which might involve making a reservation. Even though the event ticket itself might be covered in the upcoming events document, the action of booking (reserving) a ticket for someone else would touch on the reservations process.
Looking at the crossover topics: the upcoming events document handles event details and tickets, but the actual booking process—like how to make a reservation for someone else—is part of the reservations document's info on taking action (making reservations). The user's intent involves booking, which signals reservation-related procedures.
Also, the guidelines mention that if the query involves actions related to making reservations, the reservations document should be included. Even if the event details are in another document, the act of booking requires the reservations context. So the next node would need the reservations document to address the booking process aspects, like policies or steps involved in booking for someone else.
</think>
{
"reasoning": "The query asks about booking an event ticket for someone else, which directly relates to reservation or booking actions. While event tickets might fall under the upcoming events document, the act of 'booking' or reserving a ticket (especially for another person) signals reservation intent. The reservations document contains information on how to take action on behalf of a customer to make or check reservations, which is necessary context for addressing this query. Even if the event details are in another document, the reservations document is required to confirm policies or procedures around making reservations for others.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any reservations left for upcoming events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break down the user's query: "Are there any reservations left for upcoming events?" The user is asking about reservations specifically related to upcoming events.
First, I check the Reservations Document contents. It includes info on reservation policies, how to make or check reservations, and handling of groups/large bookings. However, the availability of reservations for specific events might be in the Upcoming Events Document, which lists event details like dates, times, tickets needed, etc. But the query is about the availability of reservations for these events.
The Reservations Document doesn't list event details but does cover how to check or make reservations. Even if event-specific info is elsewhere, the user's intent to reserve (checking availability) means the next node needs Reservations Document to explain how reservations are handled, policies, or how to check availability. The crossover topics don't cover reservation availability checks, which are part of the Reservations Document's action items (checking reservations).
Additionally, the Guidelines mention including Reservations if the query involves reservation actions, even if part of the answer is elsewhere. Since the user is asking about reservation availability for events, Reservations Document is needed for context on how to check or make those reservations, even if event details are in another doc.
</think>
{
"reasoning": "The query asks about reservations for upcoming events. While event details are in the Upcoming Events Document, the reservation availability check (e.g., 'reservations left') directly relates to reservation policies/actions covered in the Reservations Document. The user signals booking intent, requiring context on reservation procedures/policies to answer effectively. The Reservations Document is needed to provide context for checking reservation availability, even if event specifics are handled elsewhere.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are any of your events filling up fast for bookings?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "Are any of your events filling up fast for bookings?" So, they're inquiring about the availability of event bookings, specifically if events are getting booked quickly.
First, I need to check if the reservations document is relevant here. The reservations document contains info on reservation policies, how to make or check reservations, and details about seating and group handling. The query is about events booking up, which might relate to reservation availability.
Now, looking at the crossover topics. The upcoming events document has info on events, including whether tickets are needed and event details. However, the user's question is about the booking status—how fast events are filling up. That's more about reservation availability rather than the event details themselves. The reservations document would include policies on how bookings are handled, capacity limits, and maybe how quickly slots are taken, which the next node might need to determine if events are filling up. Even though events are covered in another document, the actual booking status and policies (like capacity) might be in reservations.
Also, the guidelines mention including reservations if the query involves whether a reservation is needed or about booking intent. Here, the user is asking about the booking status, which implies they might need to make a reservation soon, so including reservations document provides context on how bookings are managed, even if the event details are elsewhere.
</think>
{
"reasoning": "The query asks about event bookings filling up fast, which directly relates to reservation availability and booking demand. While event details are in the upcoming events document, assessing booking status requires context from the reservations document (e.g., reservation policies, capacity limits, cancellation rules). Additionally, the user's focus on 'bookings' signals reservation intent, necessitating the reservations document to inform the response.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do I need a special reservation for any upcoming events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Alright, let's tackle this query. The user is asking, "Do I need a special reservation for any upcoming events?"
First, I need to determine which document would contain the answer. The upcoming events document details events and their specifics, like whether tickets are needed. However, the user is specifically asking about reservations related to these events.
Reservations and tickets are different. The reservations document includes policies like whether reservations are required, minimum spends, or how to make a reservation. Even if the event itself is covered in the upcoming events doc, the need for a reservation would be in the reservations document.
The guidelines say that if the query involves needing a reservation, even for an event, the reservations document must be included. Since the user is asking if a "special reservation" is required, this directly relates to reservation policies, which are in the reservations doc.
Also, the next node might need the reservations document to cross-check if reservations are necessary for events, even if the event details are elsewhere. So including it provides necessary context.
</think>
{
"reasoning": "The query asks whether a 'special reservation' is needed for upcoming events. While event details are in the Upcoming Events document, the need for reservations (special or otherwise) falls under reservation policies, which are covered in the Reservations document. The document contains information on reservation requirements, group handling, and how to make reservations, which directly addresses whether reservations are necessary for events. Additionally, even if the core event information resides elsewhere, the reservations document is required to confirm reservation-related policies and procedures for events.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Is it possible to book now for next month’s events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let me analyze this query. The user is asking, "Is it possible to book now for next month’s events?"
First, I need to determine if the reservations document is relevant. The query mentions "book now for next month’s events." The key terms here are "book" and "events," which relate to reservations and upcoming events.
Looking at the reservations document's contents, it includes information on how to make reservations and check them. Additionally, the upcoming events document handles event details like dates and whether tickets are needed. However, the user is specifically asking about booking for events, which implies a reservation process. The reservations document is needed here because even though the events are covered in another document, the act of booking or reserving for those events would involve the reservation policies and procedures.
The guidelines mention that if the query involves reservation actions, the document should be included. Since the user wants to know if booking is possible, the reservations document is essential for the next node to check reservation policies and how to make them, even if event details are elsewhere.
Crossover topics check: The events are in the upcoming events document, but the booking aspect ties into reservations. Therefore, include the reservations document.
</think>
{
"reasoning": "The query asks about booking for upcoming events, which directly involves reservation actions (making a reservation for an event). While event details are covered in the upcoming events document, the act of booking/reserving requires context from the reservations document, such as policies, procedures, and how to take action. The reservations document is necessary to confirm whether reservations are possible for events and how to process them.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
How can I check booking availability for your events?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "How can I check booking availability for your events?"
First, I need to determine if the reservations document is relevant here. The query is about checking booking availability for events. The reservations document includes information on how to check a reservation, which is directly mentioned in the user's question. Even though the events are covered in the upcoming events document, the action of checking booking availability falls under the reservations process.
Looking at the crossover topics, the upcoming events document covers event details but not how to check their availability. The reservations document handles the actual checking process. Since the user is asking about the method to check availability (an action related to reservations), the reservations document should be included to provide the necessary procedures or policies on how to do that.
Also, the guidelines mention that any query involving actions related to making or checking reservations should include the reservations document. Even if the event details are elsewhere, the action here is about checking bookings, which is handled by the reservations document. Therefore, including it is necessary for the next node to provide accurate information on how to perform that check.
</think>
{
"reasoning": "The query asks about checking booking availability for events, which directly relates to reservation-related actions. The reservations document contains information on how to check reservations, which is necessary to answer this question. Even though events are covered in the upcoming events document, the act of checking booking availability requires the reservations document to explain procedures or policies around verifying existing bookings. This aligns with the guideline that queries involving reservation actions (checking, making) require inclusion of the reservations document.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there last-minute event reservations available?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's analyze this query: "Are there last-minute event reservations available?" The user is asking about the availability of last-minute reservations for events.
First, I need to check the reservations document's contents. It includes information on how to make reservations, check them, and policies like cancellations. Event-specific reservations aren't directly mentioned in the reservations document. However, events are covered in the upcoming events document, which handles event details and tickets. But the user is specifically asking about reservations for these events, which combines both events and reservations.
The crossover topics mention that event details are in the upcoming events document, but reservations for those events would involve the reservations document. The guidelines state that if the query mentions reservations, even for events, the reservations document should be included to check policies or availability. Even if the main info is in the events doc, the reservations doc is needed to confirm if last-minute bookings are possible.
So, since the query is about event reservations, even though events are a separate document, the reservations document is necessary to address the reservation aspect. Therefore, include the reservations document.
</think>
{
"reasoning": "The query asks about last-minute event reservations, which directly relates to reservation availability and policies. While event details are covered in the upcoming events document, the mention of 'reservations' triggers the need for the reservations document to address policies, availability, and procedures for making or checking reservations. Additionally, the next node may require the reservations document to validate event-specific reservation logistics (e.g., time limits, cancellation policies).",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do I need to confirm my reservation before the event?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking if they need to confirm their reservation before the event. The task is to determine whether the reservations document should be included.
First, I look at what the reservations document contains. It includes policies like cancellation, time limits, and how to check reservations. The query is about confirming a reservation, which directly relates to the actions a customer needs to take regarding their reservation. The reservations document has information on checking reservations, which would cover confirmation procedures.
Now, checking the crossover topics: venue info, menu, and events. The query isn't about venue facilities, menu items, or event details. They're specifically asking about confirming a reservation. None of the other documents cover reservation confirmation processes.
The guidelines mention that if the query involves actions related to reservations, like confirming, the reservations document must be included. Even if another document had event info, since the user is asking about their reservation (an action item), the reservations document is necessary.
Therefore, the reservations document should be included because it directly addresses reservation confirmation procedures and policies.
</think>
{
"reasoning": "The query directly asks about confirming a reservation, which relates to the 'actions on behalf of the customer to check a reservation' listed in the reservations document. The reservations document contains policies and procedures for reservation management, including verification steps. While other documents might cover events or general policies, the core of this query focuses on reservation-specific confirmation processes, necessitating the inclusion of the reservations document.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Is there a booking fee for event reservations?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let me think through this. The user is asking if there's a booking fee for event reservations. The main thing here is "booking fee" which relates to charges for reserving an event. Now, looking at the reservations document contents, it includes details like minimum spends for reserved areas, cancellation policies, and how groups are handled. But the crossover topics mention that service charges and additional fees are covered in the Venue Information Document.
Wait, but the user specifically mentions "event reservations". The reservations document covers policies related to reservations, including any fees tied to making a reservation. Even though the Venue Information Document includes service charges, the question is about a fee specifically for booking an event. The reservations document would outline if there's a fee associated with reserving a space for events, such as minimum spends or cancellation fees that might apply. Additionally, the guidelines state that even if the answer isn't directly in the reservations document, if it's needed to provide context for the next node (like checking policies around event bookings), it should be included. Since the query is about a fee tied to reservations, the reservations document is relevant here.
</think>
{
"reasoning": "The query directly asks about a booking fee related to event reservations. While service charges and additional fees are generally covered in the Venue Information Document, the reservations document explicitly includes policies like minimum spends for reserved areas and cancellation policies, which may involve fees tied to reservations. Additionally, even if the answer isn't explicitly stated in the reservations document, it provides critical context for policies around event reservations, which the next node would need to address the query fully.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I reserve a private event space?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "Can I reserve a private event space?" I need to decide if the reservations document is relevant here.
First, the query is specifically about reserving a private event space. The reservations document includes info on how groups and large bookings are handled, which would cover private events. It also has details on seating layouts and areas of the venue, which might relate to private spaces. Plus, policies like minimum spends or cancellation for reserved areas would apply here.
Looking at the crossover topics, the venue information document deals with location, facilities, etc., but not reservation procedures. The menu and events documents aren't related here either. Since the user is asking about reserving a space, the core of the query is about making a reservation for an event. The reservations document directly addresses how to make reservations and handle large groups, so it's necessary. There's no mention of events needing tickets or specific menus, so the other documents aren't relevant. Also, the next node would need the reservations document to check if private event spaces are available and their policies. Therefore, include the reservations document.
</think>
{
"reasoning": "The query explicitly asks about reserving a private event space, which directly pertains to reservation policies and procedures. The reservations document contains information on how groups and large bookings are handled, seating layouts, and reservation requirements—all critical for addressing private event reservations. Additionally, the next node would need this document to confirm availability, policies (e.g., minimum spends, time limits), and processes for making reservations. While other documents cover venue facilities or events, the query centers on reservation intent, making the reservations document essential.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
What’s the deadline to book an event ticket?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's see. The user is asking about the deadline to book an event ticket. First, I need to check if this relates to the reservations document. The reservations document includes info on reservation policies, how to make or check reservations, etc. But the query is about event tickets.
Wait, the upcoming events document covers event tickets, their dates, times, and whether tickets are needed. So normally, that's where event ticket info would be. However, the user is specifically asking about the booking deadline. Maybe the event ticket booking process is part of making a reservation? Or does the reservations document have info about deadlines for bookings?
The reservations document includes info on cancellation policies, time limits, and how to make reservations. If booking an event ticket requires a reservation, then the deadline might be tied to the reservation policies, like how far in advance you can book. Also, the guidelines mention that if the query involves whether a reservation is needed or actions related to making one, include the reservations doc.
Even though the event details are in the upcoming events doc, the actual booking process and its deadlines could be part of the reservation system. The next node might need the reservations document to confirm if there's a specific deadline for booking as part of reservation policies. Plus, the example given earlier about discounts for large bookings shows that even if the answer isn't directly in reservations, it's needed for context. So including reservations here would help provide necessary context about booking deadlines, even if the event details are elsewhere.
</think>
{
"reasoning": "The query asks about booking an event ticket, which implies a reservation or booking action. While event details are covered in the upcoming events document, the reservations document is needed to provide context on booking deadlines, policies, or procedures related to reservations. This ensures the next node can address both event-specific details and any reservation-related constraints or processes tied to the ticket booking deadline.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are reservations required for any live performances?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking if reservations are required for any live performances. I need to check if the reservations document should be included.
First, the query mentions reservations, specifically whether they're needed for live performances. The reservations document contains info on policies, including how groups or bookings are handled. Also, the guidelines say that if a query asks if reservations are required, even if it's about an event, include the reservations doc.
The upcoming events document has details about events, like tickets and dates, but reservations document has policies on whether a reservation is needed. Even though the event info is in another doc, the question is about needing a reservation, which ties directly to the reservation policies. Plus, the example given in the system message mentions that if the query asks about reservations being required, include the reservations document. So, even though the event details are elsewhere, the reservation requirement is covered here.
Also, the next node might need the reservations doc to check policies related to events, like if a reservation is necessary even if you have an event ticket. So including it provides necessary context. Hence, include.
</think>
{
"reasoning": "The query asks whether reservations are required for live performances. While details about live performances may fall under the upcoming events document, the reservations document contains critical context about reservation policies, including whether reservations are mandatory for specific scenarios (e.g., events). Since the query directly involves reservation requirements, the reservations document must be included to confirm if reservations apply to live performances and to provide policies like time limits, cancellation rules, or minimum spends that might influence the answer.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do you have an event I should book for in advance?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's tackle this query. The user is asking, "Do you have an event I should book for in advance?" Hmm, the main topic here is events, which are covered in the Upcoming Events document. But wait, they mentioned "book for in advance." Booking in advance implies making a reservation or some kind of booking for the event. Now, according to the guidelines, if the query involves whether a reservation is required or mentions booking, even if the core is about events, the reservations document needs to be included.
The reservations document has info on how to make reservations and policies around them. Even though the event details are in another document, the part about booking in advance might require checking if reservations are needed for events, which is covered in the reservations document. The next node would need that info to inform the user about booking procedures alongside event details. So even though the main answer is in the Upcoming Events doc, the reservations doc is necessary for context on booking.
</think>
{
"reasoning": "The query asks about events that require advance booking. While event details are covered in the Upcoming Events document, the mention of 'book for in advance' signals reservation intent. The reservations document contains policies on reservations, time limits, and procedures for making bookings, which are critical to confirm whether reservations are required for events and how to secure them. Including this document ensures the next node has context to address both event availability and booking logistics.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
What’s the easiest way to book a ticket for an event?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, the user is asking about the easiest way to book a ticket for an event. Let me think about this. First, I need to check if the reservations document is relevant here.
The query is about booking tickets for events. The reservations document includes info on how to make reservations, which could be related to booking tickets. But wait, there's also the upcoming events document which covers events and whether tickets are needed. However, the user is specifically asking about the method to book a ticket, which might involve the process described in the reservations document, like how to make a reservation or check availability.
Looking at the crossover topics, the upcoming events document has event details and ticket requirements, but if the actual booking process (like steps to reserve) is in the reservations doc, then it should be included. Also, the guidelines mention that even if the core is elsewhere, if there's a mention of booking, reservations doc is needed. The next node might need the reservations document to explain the booking process, even if event info is in another doc. So even though the event details are in the upcoming events doc, the action of booking a ticket would require the reservations document's info on making reservations. Therefore, include reservations doc.
</think>
{
"reasoning": "The query asks about booking tickets for events, which directly signals reservation/booking intent. While event details are covered in the upcoming events document, the specific process for 'booking' (reserving) tickets would require context from the reservations document, as it contains information on how to take action (make a reservation). Additionally, even if the answer involves event-specific policies, the reservations document is needed to ensure the next node can validate booking procedures, reservation requirements, or cancellation policies that might apply to event tickets.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Is there an event I should hurry to book?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Alright, let's break this down. The user is asking, "Is there an event I should hurry to book?" The key terms here are "event" and "hurry to book."
First, "event" likely refers to upcoming events, which are covered in the Upcoming Events Document. That document includes details about special events, their dates, times, and whether tickets are needed. However, the user also mentions "hurry to book," which implies a sense of urgency related to making a reservation or booking.
Now, looking at the Reservations Document contents, it includes information on how to make reservations and check them, as well as policies that might affect availability, like time limits or cancellation policies. Even though the event details are in another document, the action of booking or reserving a spot for the event would require knowledge from the Reservations Document.
Additionally, the guidelines mention that if the query involves whether a reservation is required or actions related to making reservations, the Reservations Document should be included. Here, the user is not just asking about the event itself but also about the need to book it quickly, which suggests checking reservation policies or availability.
The crossover topics for Upcoming Events don't cover reservation procedures or policies, so the next node would need the Reservations Document to provide context on how to book the event, any deadlines, or requirements. Therefore, including the Reservations Document is necessary to fully address the user's query about hurrying to book an event.
</think>
{
"reasoning": "The query asks about events requiring urgency in booking, which directly triggers the need to reference reservation policies (how to act) and availability checks. While event details are covered in the Upcoming Events Document, the 'book' intent and time-sensitive action ('hurry') necessitate inclusion of the Reservations Document to address reservation procedures, deadlines, or limitations that impact the urgency. The Reservations Document provides context on booking workflows and policies required to answer the 'hurry to book' aspect.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Are there any upcoming events that allow priority booking?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let me break this down. The user is asking, "Are there any upcoming events that allow priority booking?" The key here is "priority booking." First, I need to check which document contains information about upcoming events. The upcoming events document covers details like dates, times, tickets, and event descriptions. But the user specifically mentions "priority booking," which implies some form of reservation or booking process that might have special privileges.
Now, the reservations document includes policies on how bookings are made, including any special terms like priority booking. Even though the main event details are in the upcoming events doc, the aspect of how to book (especially priority) would relate to reservation policies. Additionally, even if the answer primarily comes from the events doc, the next node might need reservations info to confirm if there are specific booking procedures or requirements for these events. Since the query involves booking, the reservations document is relevant to provide context on how priority booking works, even if the event details are elsewhere.
</think>
{
"reasoning": "The query asks about 'priority booking' for upcoming events. While event details are in the Upcoming Events document, the mention of 'booking' signals reservation intent. The Reservations document includes policies on how reservations are handled (e.g., priority access, minimum spends, or procedures for securing bookings), which may directly or contextually inform the response. Even if the answer is primarily sourced from the Upcoming Events document, the Reservations document is necessary to validate if priority booking mechanisms exist and provide context for the next node to address reservation-related nuances.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Can I reserve tickets for next year’s events already?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking if they can reserve tickets for next year’s events already. The main task is to decide whether the reservations document is relevant here.
First, I check the query for any mention of reservations or bookings. The word "reserve" is right there, so that's a strong indicator. The reservations document includes info on how to make a reservation, check one, and policies around them, which seems relevant.
Next, I need to look at the crossover topics to ensure the query isn't covered by another document. The upcoming events document handles event details, dates, and whether tickets are needed, but the user is specifically asking about reserving tickets. While events are in another document, the act of reserving tickets implies a booking action. The reservations document includes how to take action like making a reservation, which applies here, even if the event details are elsewhere.
The guidelines mention that if a query involves reservation policies or actions, include the reservations document. Even if the event info is in another doc, the user's intent to reserve means the next node will need the policies and procedures from the reservations doc to answer properly. For example, checking if reservations are possible that far in advance, which the reservations doc might address.
Also, the reasoning example in the system message says that if the user signals booking intent, include the reservations doc as context. Here, "reserve tickets" clearly shows intent to book. Even though events are in another doc, the reservation process is key here.
Therefore, the reservations document should be included because the query is about making a reservation (action) related to events, even if event specifics are elsewhere.
</think>
{
"reasoning": "The query explicitly uses the term 'reserve tickets,' which directly signals reservation/booking intent. While event details (dates, tickets) might fall under the upcoming events document, the act of reserving tickets implies a need for the reservations document. This document provides context for reservation policies, procedures, and limitations (e.g., how far in advance bookings are allowed), even if the event itself is covered elsewhere. The reservations document is required to determine if reservations for future events are possible and under what conditions.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
Do any of your events have limited bookings?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break this down. The user is asking, "Do any of your events have limited bookings?"
First, I need to check if this relates to reservations. The key terms here are "events" and "limited bookings." The events part might be covered in the Upcoming Events document, which includes info on special events, their dates, tickets, etc. However, the question is about whether these events have limited bookings.
Now, the Reservations document includes policies like minimum spends, time limits, and how groups/large bookings are handled. The query is asking if there's a limitation on bookings for events, which sounds like it's about reservation policies for events. The Upcoming Events document has event-specific rules, but if the user is asking about booking limitations (like maximum capacity or reservation requirements), that's a policy aspect.
The Crossover Topics mention that Upcoming Events handle event-specific rules, but if the question is about booking limits, which is a reservation policy, then the Reservations document would include whether events have such limitations. The Reservations document also covers actions on making reservations, which is relevant here.
Additionally, the guidelines say that if the query involves whether a reservation is required, include the Reservations doc. Here, "limited bookings" implies reservation policies for events, so the Reservations document is needed to check if events have such restrictions. Even if the event details are in another doc, the reservation policies (like limits) would be here.
</think>
{
"reasoning": "The user's query about 'limited bookings' for events relates to reservation policies and capacity constraints, which are covered in the reservations document. While events themselves are detailed in the upcoming events document, the question specifically probes booking limitations—this requires checking reservation policies (e.g., maximum group sizes, time limits, or reserved area capacities). The reservations document provides context on how bookings are managed, even if event specifics are elsewhere. Including it ensures the next node can verify whether reservation policies apply to events.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
How soon should I book for an event before it sells out?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's tackle this query. The user is asking, "How soon should I book for an event before it sells out?" First, I need to determine if the reservations document is relevant here.
The main topic here is booking an event before it sells out. The reservations document includes info on reservation policies, time limits, and how groups are handled. The user is concerned about timing to secure a booking, which relates to reservation policies and possibly time-sensitive booking procedures mentioned in the reservations document.
Now, checking the crossover topics. The Venue Information Document has stuff like location, payment methods, dress code, etc., but nothing about booking timelines. The Menu Document is about products and last orders, which isn't relevant here. The Upcoming Events Document includes event details and tickets, but the query isn't about event specifics—it's about when to book, which ties into reservation policies, not the events themselves.
The guidelines mention including the reservations doc if there's any reservation intent. The user's asking about booking timing, which implies they want to make a reservation before seats are gone. Even if the exact answer might involve event popularity (which could be in Upcoming Events), the reservations doc is needed to explain booking timelines, cancellation policies, or how quickly slots fill up. The next node might need reservation context to determine if bookings are even required for events, which is in the reservations doc.
So, despite the event aspect, the core of the query is about booking timing, which the reservations document addresses. Therefore, include the reservations document.
</think>
{
"reasoning": "The query asks about booking timing related to event sell-outs, which implicitly involves reservation urgency and policies. While events are covered in the 'upcoming events' document, the need to determine 'how soon to book' directly relates to reservation availability, policies, and potential time-sensitive booking procedures. The reservations document provides context on reservation handling, cancellation policies, and group booking logistics—all critical for advising on optimal booking timing. Even if the answer requires cross-referencing event popularity, the reservations document is necessary to establish baseline booking requirements and constraints.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
<｜begin▁of▁sentence｜>
<|System|>
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the reservations 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 reservations document:
### 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.
- The general opening hours of the venue.
Information on how to take action on behalf of the customer to;
- Make a reservation.
- Check a reservation.
!Important Do not assume any other information other than the above is in the reservations document.
When analysing the information in the prompt to test query relevance, make sure that if the answer to the query lies solely in one of the listed crossover topics, you exclude the reservations document. The reasoning will be explained in the prompt. Its ts imperative that you understand that the crossover topics are their own seperate documents and the reservations document should only be included if the query is about reservations or if the reservations document is needed to provide context for the next node.
The menu document, venue information document, and upcoming events and opening hours document are all seperate documents that have their own topics. If the query is solely about one of these topics, the reservations document should be excluded.
Make sure to follow the rules set out in the guidleines section of the prompt. To ensure you are making the correct decision.
Please make sure to parse your "reasoning" and "decision" and output them in the following json format.
Ensure you follow the following json schema no matter the query you are working with:
EXAMPLE JSON OUTPUT:
```json
{{
"reasoning": "The reasoning as to why the document should be included or excluded",
"decision": will be either "include" or "exclude"
}}
```
### END OF EXAMPLE ###
<｜User｜>
Look at the following query:
### QUERY ###
What events do you have open for reservation now?
### TASK ###
You are responsible for making a decision on whether the reservations document shown to you in the system message is relevant for answering the user query. And should be included in the context for the next nodes repsonse.
Below are crossover topics that are in other documents, if the query is solely addressed by one of these topics, the reservations document should be excluded. As the relevant context will lie in the other documents.
### CROSSOVER TOPICS - NONE OF THESE ARE IN THE RESERVATIONS DOCUMENT - THESE DOCUMENTS AND TOPICS ARE THEIR OWN SEPERATE DOCUMENTS ###
### VENUE INFORMATION DOCUMENT CONTENTS ###
- Service charges & all other additional charges.
- Venue location and accessibility.
- The venues policy on tipping.
- Rules around bringing outside food and drink into the venue.
- Rules on storing unfinished alcohol for later consumption.
- Information on the venues facilities. i.e wifi, power outlets, parking, restrooms etc.
- Rules on bringing pets.
- Smoking policy.
- Accepted payment methods by the venue such as; line pay, cash, credit card, yo-yo card etc.
- Minimum Spend Policy(per head).
- Dress code.
### MENU DOCUMENT CONTENTS ###
- Detailed information/descriptions off all the products on the menu, including ingredients and prices.
- Last orders times for the kitchen and other product serving facilities.
### UPCOMING EVENTS DOCUMENT CONTENTS ###
- Special one-off events (if any).
- Weekly events (if any).
- Monthly events (if any).
- Each event will have information 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 speical occasions like a business aniversary, New Year's Eve, Christmas, etc.
### GUIDELINES ###
Any query that is solely about a product will be answerable by the menu document. So long as there are no mentions of reservations or bookings in the query the decision in this case should be to exclude the reservations document.
You also need to consider that the next node will require this reservations document to proof check everything related to reservations even if the document itself cannot directly answer the question.
For example if a customer asks if there a special discounts for large bookings. The next node will need the reservations document to check whether large bookings are even possible, in this case the document will provide essential context even if it cannot full answer the query.
If the query is asking whether a reservation is required for any reason, even if the core of the query lies elsewhere. The reservations document MUST be included to provide context about the reservation policies and procedures that might be relevant to the query.
However, if the query is about specific events, festivals, themes, or menus, AND DOES NOT involve reservation policies, seating layouts, or whether a reservation is needed, actions related to making or checking reservations or whether reservations are neccessary for such events.
The reservations document should be excluded as in such cases, the reservations document would not provide any useful context.
<｜Assistant｜>
<think>
Okay, let's break down the user's query: "What events do you have open for reservation now?" The key part here is "open for reservation." The user is asking about events that can currently be reserved.
First, I check the reservations document contents. It includes info on how to make reservations, policies, and actions like checking or making reservations. The upcoming events document handles event details like dates, times, tickets, etc. But the user specifically mentions reservations for events.
Even though event details are in the upcoming events document, the act of reserving or needing a reservation would involve the reservations document. The guidelines say if the query involves whether a reservation is required or actions related to reservations, include the reservations doc. Here, the user is asking about events that are open for reservation, implying they want to know which events can be booked.
The next node might need reservation policies (like how to book, minimum spends, etc.) to fully answer. So even though the events are listed elsewhere, the reservation aspect requires including the reservations document.
</think>
{
"reasoning": "The query asks about events 'open for reservation,' which directly ties to booking/reservation intent. While event details are covered in the Upcoming Events document, the reservations document is required to provide context on reservation policies, procedures (e.g., how to reserve), and whether reservations are necessary for specific events. This ensures the next node can address both event availability and the reservation process.",
"decision": "include"
}
<｜end▁of▁sentence｜>
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.