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
Prefix | IRI |
n5 | http://www.openvoc.eu/poi# |
schema | http://schema.org/ |
rdf | http://www.w3.org/1999/02/22-rdf-syntax-ns# |
n2 | http://data.yelp.com/Review/id/ |
rev | http://purl.org/stuff/rev# |
n4 | http://data.yelp.com/Business/id/ |
xsdh | http://www.w3.org/2001/XMLSchema# |
n7 | http://data.yelp.com/User/id/ |
Statements
- Subject Item
- n2:BMFqWZbKaDyGveAX6TN7gw
- rdf:type
-
rev:Review
- schema:dateCreated
-
2018-02-22T00:00:00
- schema:itemReviewed
-
n4:zr42_UsWfaIF-rcp37OpwA
- n5:funnyReviews
-
1
- rev:rating
-
2
- n5:usefulReviews
-
1
- rev:text
-
While the atmosphere & location are great, the service & food quality leaves much to be desired. This is my second time visiting this location and while the first time wasn't an exceptionally memorable experience, this second visit had our party of 3 saying, "We will never go back."
At 1PM on a Sunday, we were quoted a 1-hour wait time (fine), so we headed to the bar to have a drink while we waited. Not once did the bartender smile, engage or ask if we needed anything. Instead, we were made to feel like a burden.
The entire dining experience took over 2.5 hours. We didn't end up having to wait an hour for our table (yay), but we did wait an hour for an appetizer (which was not what we ordered because they were out of what we requested) to arrive. When our entrées finally came, the salad I ordered was wrong and the chicken overcooked and tasteless. Charges on our check were also incorrect. The entire experience was just no bueno. With so many other brunch options in the valley, this is a hard no for me.
- n5:coolReviews
-
0
- rev:reviewer
-
n7:9fJlO9PuoFMtDKsvpBVzwA