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
n7http://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#
n5http://data.yelp.com/User/id/

Statements

Subject Item
n2:0h65gGvUe3TCeWDmzPEsGQ
rdf:type
rev:Review
schema:dateCreated
2017-07-04T00:00:00
schema:itemReviewed
n6:ZL2QeOMAPXthvBmng5RN-Q
n7:funnyReviews
0
rev:rating
1
n7:usefulReviews
1
rev:text
Worst Pizza Hut of all time. Patrons beware. This is unfortunately the closest one to our house and ever since Pizza Hut launched their online $10/Pizza of the day, we began ordering more Pizza Hut the ever before in life. Unfortunately, there are a slew of issues with this location and not once but a handful of times now, we have not received our orders. It's always one pathetic excuse after another. Staff explanations always end up reflecting something that is ultimately not the customers problem. And whenever they mess up, their only resolution is to offer 20% off your order. Last time, an hour after we ordered online, 15 minutes past expected delivery time, no pizza. They blamed an online ordering glitch (not my problem), and said that our pizzas actually hadn't been made yet because no driver was available (again, not my problem). FYI, your Pizza isn't prepared for delivery til a driver shows up at the store. How do you market and actively offer delivery as a feature, yet, the system is so faulty? It's not a Pizza Hut franchise issue, it's this location. Terrible customer service, and often the food isn't quite up to par either. Take some extra time and order from another location. That's what I do.
n7:coolReviews
0
rev:reviewer
n5:G2dZ7j7lhxu6rkS4Hn9NoQ