In this task, you're given reviews from Amazon's food products and a summary of that review. Your task is to classify whether the given summary matches the original review. Generate "True" if the given review and its summary match, otherwise generate "False".

Input: Consider Input: Reviews: The big cup broke mid-blending and everything flew out all over my kitchen. This was the second time I ever used it
Summary: The big cup broke mid-blending and everything flew out all ...

Output: True

Input: Consider Input: Reviews: Horrible! This bra was so small there was no possible way it was ever supposed to be the size I requested. It shipped from China. It took forever to arrive and now I can't even return it. When I reached out to the seller, she suggested they send me ANOTHER bra in another size. If THIS bra was 8 sizes too small, how can I expect ordering the biggest size you make will reasonably accommodate my breasts?? Shout out to Buzzfeed for LYING about how well this slingshot fits. *rolls eyes*
Summary: Girls with sizable boobs, don't even think about it!

Output: True

Input: Consider Input: Reviews: A little Background: I am proficient in Javascript and PHP, so this isn't my first language. I have also taken a full C# course on Udemy that was about 18 hrs long and have been writing code for about 2 years consistently (nearly daily) as a hobby... NOW.. The Good: I think that this entire book series is GREAT for SUPPLEMENTAL learning. It's really nicely structured and provides a lot of great code examples and you know exactly what your looking at. It's so good in fact, that I would probably buy the second and third books in the series (mainly the third) again just for reference. The Bad: My two biggest criticisms of this book are its redundancy and not beginner friendly (which is in the title)... This book is far more code than explanations. This is not a problem in itself, however, There is often little to no deep explanation along with each example and it commonly repeats the phrase "this will be discussed in more detail later". Most of the code shows you how to write things, but no real explanation on how to use what you would have learned. A large portion of the book is spent repeating itself in explaining how the code would look if you used another data type (basically changing out 1 word). So for people who haven't written a line of code before, the best way I could explain is, if the author was describing a ball: If you don't understand this, don't worry. It will be discussed in more detail later. This is a ball and what it looks like: // Some block of code that shows a ball If you don't understand this, don't worry. It will be discussed in more detail later.This is a blue ball and what it looks like: // Some block of code that shows a blue ball If you don't understand this, don't worry. It will be discussed in more detail later.This is a red ball and what it looks like: // Some block of code that shows a red ball If you don't understand this, don't worry. It will be discussed in more detail later.This is a green ball and what it looks like: // Some block of code that shows a green ball If you don't understand this, don't worry. It will be discussed in more detail later.This is a purple ball and what it looks like: // Some block of code that shows a purple ball ...Anyways that's pretty much what this book is. If that's what you're looking for, that's what it has. Buy it or don't....
Summary: Maybe next time put more stuffing pop plastic for safe packaging
Output: False