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/
n7http://data.yelp.com/Business/id/
revhttp://purl.org/stuff/rev#
xsdhhttp://www.w3.org/2001/XMLSchema#
n4http://data.yelp.com/User/id/

Statements

Subject Item
n2:KlXucma9xMEsWWUNZlwHlA
rdf:type
rev:Review
schema:dateCreated
2018-02-18T00:00:00
schema:itemReviewed
n7:ngs16C2M_uTq2zXamltHVw
n5:funnyReviews
0
rev:rating
1
n5:usefulReviews
0
rev:text
Foods good, but the chairs are falling apart and the place seems kinda dirty and the food isn't cheap, it's a real hole in the wall. Despite that I wanted to return the next day I call to place an order, but they ran out of meat, so whatever I figure I come back tomorrow. Next day I come in, same issue no meat other than spareribs, I find this out after waiting for two, " people" to ask every question under the sun about portion sizes. These two somewhat minor inconveniences and the fact the location is out of the way is keeping me from ever returning again, there's a lot of good BBQ places here to spend money at that are much more convenient. It explains why each visit I made only 3 people were there despite the food being good quality, maybe I'll try them again in 2019. Quick update owner responded to my benign review, I decided to change to a 1 star from a 3 star, weirdest customer service exchange of my life. He sends me string of snarky PM's then publicly post a professional response, one that I would have expected In the beginning, but did not receive until posting my PM's. Sure I can't wait to return lol.
n5:coolReviews
0
rev:reviewer
n4:ZW0Aq6LthdFXP9nhRfiBvg