This HTML5 document contains 9 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
n5http://www.openvoc.eu/poi#
schemahttp://schema.org/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n2http://data.yelp.com/Review/id/
revhttp://purl.org/stuff/rev#
n4http://data.yelp.com/Business/id/
xsdhhttp://www.w3.org/2001/XMLSchema#
n7http://data.yelp.com/User/id/

Statements

Subject Item
n2:vsYHClZz51C8C15pc8ma3w
rdf:type
rev:Review
schema:dateCreated
2016-02-09T00:00:00
schema:itemReviewed
n4:htNS19kbvYpQ5FfW0_-f8g
n5:funnyReviews
0
rev:rating
2
n5:usefulReviews
1
rev:text
Our party of 4 arrived on a Saturday night, with 6:30pm reservations. The hostess proceeded to tell us that there was a full house tonight, and so entrees will take a while to come out. She recommended that we order a bunch of appetizers in the meantime. We all thought this was strange because first, shouldn't a restaurant be able to handle a busy night, second, there were empty tables on the ground floor, and three - she didn't even apologize for a possible delay in our orders. Our waitress shows up to take our drink and appetizer orders. The appetizers came out in a fairly short amount of time, but we had to wait over 15 minutes for our drinks. Her explanation - the bartender is in training and so our specialty drinks take longer. So, the restaurant has a busy night and they have a bartender in training working this evening? Finally, there was no issue getting our entrees, but getting the table cleared of our dirty dishes took over 20 minutes (and two requests to the waitress). After the table was cleared, we had to wait another 15 minutes for the check. All in all, I won't go back. The food was good, but definitely not worth the poor service.
n5:coolReviews
0
rev:reviewer
n7:LRAPQRAUNST4hA64CfNqug