Products -> Semantic Analysis for Restaurant Reviews
Semantic Analysis for Restaurant Reviews consists of 128 Semantic Models. Each Semantic model was especially designed, built, tested, and re-tested on hundreds of thousands of restaurant reviews from multiple sources. All presented Semantic Models work with an unparalleled precision of 90-95%.
Below, you will find a high-level view of all semantic models designed for restaurant reviews.
In other words, what type of information do we garner from reviews.
Client loyalty & Recommendations
Will he come back? vs. not come back?
Will he recommend it? vs. not recommend?
Overall good/satisfied. vs. Disappointed?
Is it good for kids? Couples? Special occasions? Meeting friends? Family meetings?
Restaurant’s General Opinions
Is the restaurant clean? Dirty? Renovated? Outdated? Smelly?
Need to wait for a table? Can’t book a table?
Need a reservation? Reservation problems?
Is it kids friendly? Has it got changing facilities, play area, got kids menu?
Critical (dangerous to the brand) opinions
Hair in Food, Food poisoning, Bugs/Insects,
Restaurant was not as advertised,
Dirty restaurant, Service unpleasant/unprofessional
Food Taste & Quality Opinions
Food was tasty? Delicious? Mediocre? Poor? Bad? Tasteless?
Low-quality ingredients? Fresh? Poorly presented? Healthy food? Greasy? Unappetising? Perfectly cooked?
Opinions about specific dishes
Was a chicken tasty? Ws spaghetti ok?
Were grilled vegetables crispy?
Was the dessert fabulous?
Food Variety & Selection Opinions
Vegetarian menu? Vegan options? Gluten-free options?
Good wine/drinks selection? Good beer selection?
How about the menu? Limited? Rich?
Staff was friendly? Professional? Rude?
Waiting time was acceptable? Is delivery time quick?
Manager: friendly? Professional? Available?
Service was quick, slow? good?
Wifi - is it free? Is it fast?
Does parking have lots of spaces? limited? lack of parking?
Is suitable for a wheelchair? Is there good ventilation? AC?
Was it overpriced? Cheap, expensive? Was it worth them money?
Is there a service charge? Any additional fees? Bill problems?
Only cash payment?
Nice vibe? Cozy, relaxing atmosphere? Pleasant? Unpleasant vibe?
Was it not welcoming? Was the decor nice? Interior outdated?
If you want to get custom-made private API with different models, or receive more info about the custom On-Premise version with 0 cents/text (BIG DATA Compatible)
Search based on your individual preferences matched with opinions of similar people to you and data from reviews
What is important to you? Personalize your search
Our AI remember these parameters while reading millions of reviews and find you the best possible place
Our AI deeply analyzed 4.4 million reviews to match your personal needs and chose these places:
Meet the Alchemist Foodie. He has eaten everywhere and he has read all reviews in the world (and he remembers them all).
He is patient and he can spare a moment to find you new interesting places.
Instead of reading thousands of reviews individually, you can see a semantic summary and get a feeling for what is contained within them in 20 seconds. You can click for specific information and see extracted sentences from reviews.
Restaurantrestaurant in generaldecor nice 33 renovated 18 clean 15
Opinions & Recommendationsopinionoverall satisfied 34 will return 24 will recommend 9
Servicestafffriendly 23 competent 11 understaffed 9 unfriendly 4 uncompetent 2
Pricerestaurantexpensive 13 overpriced 9 adequate price 6
Foodtastedelicious 41 mediocre 5
Favourite dishesitalian pasta delicious 21 big portions 20
Addonswififree 13 problem 7 slow 4
The automatic summary made from reviews - after processed by our API (no additional NLP/NLU/ML or post-processing needed).
The first no-block title (Restaurant, Food etc.) is a Category from our API, blue blocks (Opinion, Staff etc.) are Aspects, green and red blocks (decor nice, renovated etc.) is the Feature and Polarity (Feature is text, Polarity is color).
See the live demo of semantic summary made from hotel reviews (powered by our technology).
First, you process all reviews of a given restaurant for a period of time (e.g. last 6 months) and extract important information with high accuracy. Then, it is easy to compare these results with other restaurants, and valuable patterns emerge.
Our AI deeply analyzed all 4489 of your reviews, compared with 1 200 000 reviews of similar businesses and extracted 11 Recommendations/Tips how you can improve your business:
Compare your parameters with similar businesses
Here, we focused on showing classified negative opinions critical to restaurant owners and presented on a brand reputation dashboard.
Slow service (5 mentions):
"We needed to wait for the order 30 mins!"
"Food is great, but very slow service..."
"waited with my friends 25 mins to order"
"great if you don't mind waiting"
"was hungry and waited almost an hour for the food"
By clicking on specific semantic category (here: Slow service) we get specific sentences/segments and "not the whole review" where people mentioned that the service was slow. We detect all the information that is correlated to slow service (e.g. "needed to wait", "if you don't mind waiting"), not just with keywords (e.g. slow, service). This is the advantage if you use Human-like Analysis (Semantic Analysis) instead of keywords.
You can see what reviews are about in 10 seconds. By clicking on specific information, you can go deeper (data zoom-in) and display actual sentences (not whole reviews).
Our AI deeply analyzed 3344 Reviews and organized them for you
(so you do not have to read them all)
|People was the most satisfied with:|
|Friendly, attentive Staff||
|Tasty, flavoursome Food||
|Cosy, relaxing Vibe||
|People complained about:|
|Restaurant dark, no light||
|Food not tasty||
|Problem with WiFi||
|show me more...|
By understanding a review better, you are able to provide deeper and easier-to-understand analysis for your clients.
Positive vs. Negative
Overall good/satisfied vs. Overall dissapointed
Will come back vs. Will not come back
Will recommend vs. Will not recommend
Language has color. Do not reduce it to black & white.
Information extracted by 128 Semantic Models is precise enough to create automatic text summary.
Natural Language Generation Summary from Reviews could look like this:
Our AI deeply analyzed all your reviews for the past 3 months, combined them with reviews of similar businesses and created this summary:
Almost everyone were satisfied with the service (in 87% of reviews) and friendly staff (72%), lot of them would come back (45 mentions) and will recommend this restaurant (33m.).
Reviews stats that restaurant is tiny (17 m.) but have romantic vibe (13 m.), which suits for a date (12 m.).
Unfortunately, customers complain about small portions (8 m.) and not enough spices in their food (5 m.).
Overall they think that it is expensive place (7 m.) but worth the money spend (13 m.).
|Semantic distribution summary out of text:|
|Would come back||
|Good for a date||
|Worth money spend||
Want to talk more about these solutions?
Example restaurant review:
Simplified output after processing by Semantic Analysis for Restaurant Reviews:
|1.||We are going to this place every sunday with my family||
good for family meeting +1
|2.||I love chicken masala there and i was not dissapointed, delicious||
food: chicken masala
|3.||We took pad thai as well and I must say it was not so tasty as other dishes||food: pad thai not tasty -1|
|4.||My wife and kids love there, they got a special kids menu, changing table and staff is friendly too||
kids menu available +1
changing facilities available +1
service staff friendly +1
|5.||As we were leaving the jazz band started to play and there was a lot of young people and you can feel the good vibe in the air||
live music nights +1
|6.||So, I recommend for a family, even for a friends meeting at evenings, do not recommend to a business meeting or romantic dinner)||
good for family +1
good for meeting friends +1
good for family +1
not good for business meeting -1
not good for romantic evening -1
We specialize in creating dedicated Language Understanding APIs for specific reviews or other user-generated content. We focused in travel, food, apps, surveys, profanity & toxicity detection and prepared a set of Language Understanding APIs for these domains. We also develop private custom-made Language Understanding APIs for any kind of text (reviews, comments, or other user-generated content). Contact Us to discuss what is possible, or Send Us Your Dataset to see how it works on your data.
We stand by the statement that we detect more information than Watson or than any other Deep Learning solution and we are more accurate than Google in a specific domain. We are also much more cost-effective. And we allow the processing of as much data as you want with no additional cost (0 cents / text).
This is possible because we created the next-generaion process of developing NLU systems in which we can build Semantic Models 10 x faster. It is designed from the ground up to process reviews and other user-generated content, not proper english texts. It is the result of 13 years of experience in NLP/NLU, 8 years in processing reviews, and more than 50 implementations (2007-2020) in companies, corporations, and startups of NLP/NLU systems and Language Understanding APIs to process reviews and other user-generated content.
We are passionate and proud of our technology and aim to provide the optimal technology for reviews and other user-generated content. We will be happy to help you implement your brilliant ideas and discover what is possible.
|"Breakfast was tasty"||=>||Breakfast: positive|
|"Breakfast was huge"||=>||Breakfast: positive|
|"Breakfast was not included"||=>||Breakfast: negative|
|"Breakfast was very tasty but limited choices"||=>||Breakfast: neutral|
|"Breakfast was delicious but you had to pay extra"||=>||Breakfast: neutral|
|"Breakfast was tasty"||=>||Breakfast: tasty|
|"Breakfast was huge"||=>||Breakfast: plenty options|
|"Breakfast was not included"||=>||Breakfast: not included|
|"Breakfast was very tasty but limited choices"||=>||Breakfast: tasty | poor, limited|
|"Breakfast was delicious but you had to pay extra"||=>||Breakfast: tasty | not included|
Language has colors. Do not reduce it to black & white.
Technological differences of Unicorn NLP Cognitive Learning solution (compared to other NLP/NLU/ML/DeepLearning solutions):
The semantic model is the newest approach to information extraction models where boundaries of those models are not determined by the structure of a language (or grammar, or used words), but the type of information you are detecting. It does not matter how the user writes an opinion about a specific object, e.g. “breakfast was a joke”, “Muffin and cold coffee is not a breakfast”, “Breakfast wasn’t included as written”, our semantic model still detects it and provides structured-data. With "breakfast" example, it is relatively easy to provide a shallow analysis (e.g. Sentiment Analysis) with the current NLP techniques. If you are looking for more sophisticated information (e.g. is it safe?, is it handicap friendly?, will someone come back?, Is it sustainable? Is it pet-friendly?) the situation gets more complicated. Current techniques provide a part of this information and their accuracy relies on the keywords used in reviews. Users are very creative in the reviews and they are not using a keyword approach. Let’s take one example. If we want to answer the question “is it safe?”, you need to capture a lot of information from reviews without common keywords safe/dangerous. In practice, they write this in tens or hundreds of ways: e.g. “there was a lot of drunken people outside”, “I did not feel good because of the neighbors”, “someone yelled in the night and the front desk lady did nothing”. We believe that if the human can understand what is written in the review, then technology should detect it as well. That is why we call them Semantic Models, not information extraction models.
Our Unicorn NLP Cognitive Learning Environment is a place where we design and precisely craft all the semantic models. It is a perfect combination of human and computer intelligence. It is the result of 13 years of experience in the NLP/NLU field and 50+ implementation in 2007-2020. It is the secret sauce of our technology, and it allows us to deliver the best technology in the world for reviews and other user-generated content. Statistical algorithms provide the data based on the processing of hundreds of thousands of reviews, but the humans are making all the crucial decisions. Human does not only annotate the data (like in machine learning approach), but also create semantic boundaries, semantic rules, domain-specific dictionaries, describe common domain-specific misspellings and grammar errors, and whatever it takes to achieve precision=90-95%. Given the pace of AI development, this is a significant advantage in information extraction (in NLP/NLU), and it will be appropriate for the next decade. Think about our environment as a way of creating tens of thousands of very precise, hand-crafted semantic rules but with an AI as an assistant rigorously validating new ideas and marking parts of algorithms and semantic code that needs improvement. AI assistant provides new ideas based on constant simulations on real data and tens of statistical tools.
We designed a unique semantic programming language (QL4Reviews) to extract information from reviews and other user-generated content. With this programming language, you build semantic models ten times faster than in other current technologies. Every Semantic Model is programmed in QL4Reviews and consists of 50-2000 lines of semantic code. Heavily optimized engine allows processing through 150+ Semantic Models on 1 medium-CPU Amazon AWS instance - 1 million reviews a day. The speed of the core engine was essential for us from the beginning. It helps us daily speed the process of development and make several iterations and validation on data a day.
Our technology is designed from the ground up to process reviews and other user-generated content, not proper-grammar texts. It's resistance to errors allows processing also machine-translated reviews/texts (via Google Translate or Microsoft Translate). This approach provides almost as good results as processing English reviews but there is no need to rewrite and maintain semantic models into other languages. Consequently, it is a much more cost-effective solution, and it is easier to maintain and scale (using Google Translation API allows you to process 105 languages on day one).
Read more & See demo: Processing machine-translated non-English Travel Reviews
This is not just another limited black box that you still need to configure to your data, and learn how to use it. You get dedicated Language Understanding API with a human-like accuracy, which is train&tested on your data. We redesigned every layer of technology and we wanted to address the biggest challenge in the NLP/NLU industry. We wanted to change the way you use and think about Natural Language Understanding API. In our opinion, if you are using NLP API, you should not get your hands dirty and spend inordinate time thinking about how to best implement this API into your application. We wanted to hide all the NLP complexity inside the system and provide you ready-to-use data. We believe that NLP API should be simple and easy to use without linguistic, machine learning or other expertise. You do not need to spend weeks on improving the accuracy of "domain-independent" NLP API, to adjust to Your domain or to make decisions about complex output parameters. Getting output parameters like confidence (e.g. 0.7852) or polarity (e.g. 0.4352) or keywords detected (e.g. friendly, 0.6786; disappointed, -0.7564) gives every developer problems and frankly, they are not standard or predictable. They are rather a consequence of used technology inside, and putting these parameters for the output in our opinion, is the way to leave configuration and responsibility for decision-making to You. We believe in simple human-like output where a human can understand what this API detected. We believe that we have developed excellent semantic models for specific domains, so you can get tailored results and focus on your business. We position ourselves as a read-to-use technology, not a standard API that is a tool that you need to configure and train to your data.
If you want to get custom-made private API, or receive more info about the custom On-Premise version (with 0 cents/text),
or want to discuss what is possible
If you want to test it or see how it works on your data, send us a dataset
(we do not collect your data)