text
stringlengths 7.1k
9.55k
|
|---|
<|im_start|>system
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<|im_end|>
<|im_start|>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.
<|im_end|>
<|im_start|>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"
}
<|im_end|>
|
<|im_start|>system
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<|im_end|>
<|im_start|>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.
<|im_end|>
<|im_start|>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"
}
<|im_end|>
|
<|im_start|>system
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<|im_end|>
<|im_start|>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.
<|im_end|>
<|im_start|>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"
}
<|im_end|>
|
<|im_start|>system
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<|im_end|>
<|im_start|>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.
<|im_end|>
<|im_start|>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"
}
<|im_end|>
|
<|im_start|>system
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<|im_end|>
<|im_start|>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.
<|im_end|>
<|im_start|>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"
}
<|im_end|>
|
<|im_start|>system
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<|im_end|>
<|im_start|>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.
<|im_end|>
<|im_start|>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"
}
<|im_end|>
|
<|im_start|>system
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<|im_end|>
<|im_start|>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.
<|im_end|>
<|im_start|>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"
}
<|im_end|>
|
<|im_start|>system
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<|im_end|>
<|im_start|>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.
<|im_end|>
<|im_start|>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"
}
<|im_end|>
|
<|im_start|>system
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<|im_end|>
<|im_start|>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.
<|im_end|>
<|im_start|>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"
}
<|im_end|>
|
<|im_start|>system
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<|im_end|>
<|im_start|>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.
<|im_end|>
<|im_start|>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"
}
<|im_end|>
|
<|im_start|>system
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<|im_end|>
<|im_start|>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.
<|im_end|>
<|im_start|>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"
}
<|im_end|>
|
<|im_start|>system
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<|im_end|>
<|im_start|>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.
<|im_end|>
<|im_start|>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"
}
<|im_end|>
|
<|im_start|>system
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<|im_end|>
<|im_start|>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.
<|im_end|>
<|im_start|>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"
}
<|im_end|>
|
<|im_start|>system
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<|im_end|>
<|im_start|>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.
<|im_end|>
<|im_start|>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"
}
<|im_end|>
|
<|im_start|>system
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<|im_end|>
<|im_start|>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.
<|im_end|>
<|im_start|>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"
}
<|im_end|>
|
<|im_start|>system
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<|im_end|>
<|im_start|>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.
<|im_end|>
<|im_start|>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"
}
<|im_end|>
|
<|im_start|>system
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<|im_end|>
<|im_start|>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.
<|im_end|>
<|im_start|>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"
}
<|im_end|>
|
<|im_start|>system
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<|im_end|>
<|im_start|>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.
<|im_end|>
<|im_start|>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"
}
<|im_end|>
|
<|im_start|>system
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<|im_end|>
<|im_start|>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.
<|im_end|>
<|im_start|>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"
}
<|im_end|>
|
<|im_start|>system
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<|im_end|>
<|im_start|>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.
<|im_end|>
<|im_start|>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"
}
<|im_end|>
|
<|im_start|>system
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<|im_end|>
<|im_start|>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.
<|im_end|>
<|im_start|>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"
}
<|im_end|>
|
<|im_start|>system
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<|im_end|>
<|im_start|>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.
<|im_end|>
<|im_start|>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"
}
<|im_end|>
|
<|im_start|>system
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<|im_end|>
<|im_start|>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.
<|im_end|>
<|im_start|>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"
}
<|im_end|>
|
<|im_start|>system
You are document classifier working for a bar/restaurant. You are in a node that is responsible for making a decision on whether the 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 ###
<|im_end|>
<|im_start|>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.
<|im_end|>
<|im_start|>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"
}
<|im_end|>
|
End of preview. Expand
in Data Studio
README.md exists but content is empty.
- Downloads last month
- 6