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

Statements

Subject Item
n2:VwO_h4v8e60SQvhp4Ad9XQ
rdf:type
rev:Review
schema:dateCreated
2013-06-05T00:00:00
schema:itemReviewed
n5:XmsBtCykUtObXg4Q1mYpvg
n3:funnyReviews
2
rev:rating
3
n3:usefulReviews
7
rev:text
Graze is a spot I am always returning to hoping it will be better than last time. Now, don't get me wrong - I like their food, I really do. Their burgers are tasty, their fries are great, and their brunch menu is really nice as well. But, they just aren't consistent. When I say that, I mean 3 people could order the same things and each of them would turn out differently. One person would have soggy fries and an under-cooked burger, one person could have perfect fries but an over-done burger, and one person could have everything perfect. It's just so random how things will turn out. The recipe is right: locally sourced, high quality, ingredients. A menu that is diverse but simple, and decent prices. They just need to make sure that food is just right when it goes out. A great example is one time I had brunch and my toast had mold all over it. Super gross, right? Well, the waitress and chef agreed. They were very apologetic, gave me new toast, and covered my meal. But why the hell did I get served moldy bread i the first place? It wasn't exactly hidden, you know? Luckily the rest of my meal was very good and I gave them another chance, but I know a lot of people who would have never gone back. Someday I hope I get to upgrade them to 4-stars, because I sure do want to.
n3:coolReviews
0
rev:reviewer
n7:jlXLXdWqx-KCsHLr9sE7Ow