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
n3http://www.openvoc.eu/poi#
schemahttp://schema.org/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n2http://data.yelp.com/Review/id/
n6http://data.yelp.com/Business/id/
revhttp://purl.org/stuff/rev#
xsdhhttp://www.w3.org/2001/XMLSchema#
n7http://data.yelp.com/User/id/

Statements

Subject Item
n2:I91Wl8d0GP8xPpnr3jIqIw
rdf:type
rev:Review
schema:dateCreated
2009-12-30T00:00:00
schema:itemReviewed
n6:lqtybK6_GjSqhK8U55Mc7w
n3:funnyReviews
2
rev:rating
2
n3:usefulReviews
2
rev:text
If I were just reviewing for the food, my review would be much higher.. But, considering this was the absolute slowest service I've had in as long as I can remember, that cannot go forgotten. Our server seated us in a section with only one other group there and first made us wait about 8 minutes before even bringing us water and menus. Of course, we had to wait far longer than necessary before we could order. We decided to each get entrees and then split an appetizer. By this time, the other group in our section had already left (so in other words, this place is not busy, and in fact fairly empty) and we had to wait over 30 or 40 minutes for our *appetizer*. The waiting's not over. Then the waitress brought out my friends' food about 10 full minutes before mine. (By this time, it had already been at least an hour from when I ordered), Q. Did I order something special or difficult? A. No. I ordered soup. By the time it came for paying and getting our check, we thought our server must have gone on break or something. It was beyond ridiculous how inattentive she was. The entire experience took about 2 hours in total in a not-busy restaurant. Good thing the food was fairly tasty, but that wasn't enough to get out the bad taste in my mouth about the service.
n3:coolReviews
1
rev:reviewer
n7:B0GsQE27QRV1KimXrP88rg