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:3n7jffg35iMbqB5Lf9Rwiw
rdf:type
rev:Review
schema:dateCreated
2014-04-21T00:00:00
schema:itemReviewed
n6:cKgUCzMGuRgkbKXUsgeXUw
n3:funnyReviews
0
rev:rating
2
n3:usefulReviews
0
rev:text
WHAT A DISAPPOINTMENT!!! The ambience is killer, the host staff is extremely friendly, wonderful patio in the perfect location...The menu looks (imagine this word italicized) deliciously appealing and even boasts how the chef was on some famous cooking show...so my question becomes even more desperate as to why..WHY is the food so terrible?? And by terrible I mean YUCK, EWW, "Are you serious?!?" terrible. From start to finish, everything was bad. We ordered an appetizer no onions...it came out seemingly floating in onions. Ok, no big deal, mistakes happen...Then we ordered 3 tacos each. So we're talking a 6-taco chance to pull together a decent taco...yet not a one passed. My mango in my salmon mango taco was literally green and hard (so under ripe I'm wondering how they even cut into it). The cactus in our cactus tacos was cold. The tortillas were also cold and couldn't possibly be any smaller. The fried fish taco tasted like lukewarm grease and frankly I can't recall the 3 remaining tacos we ordered because everything was so bland, meh, and unmemorable. The only reason this places gets any stars is again the ambience. Who knows? It might be an ok place to go for drinks (I probably won't bother finding out)..just DON'T ORDER ANY FOOD!
n3:coolReviews
1
rev:reviewer
n7:jJIriBAK5tPMbM5U79-Ieg