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 |
|---|
| n3 | 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# |
| n5 | http://data.yelp.com/Business/id/ |
| xsdh | http://www.w3.org/2001/XMLSchema# |
| n7 | http://data.yelp.com/User/id/ |
Statements
- Subject Item
- n2:gdX0XXCcLUnORTBfDVj2Jw
- rdf:type
-
rev:Review
- schema:dateCreated
-
2017-04-23T00:00:00
- schema:itemReviewed
-
n5:fkH7X87RFAJrj81nOZPaNw
- n3:funnyReviews
-
1
- rev:rating
-
1
- n3:usefulReviews
-
0
- rev:text
-
I so want to leave a high rating! Having been a fan of Fuego for many years, my last visit 6:30P 4/19 stunned me. I took my folks for dinner. Took 2.25 hours, with a very long wait for everything. We thought it might be an issue in the kitchen (I could see three cooks playing with the piping bag for mashed potatoes forever) but it included the salads, drink orders, and entrées. Can't blame the oven for an hour wait for salad course! Dad's steak was cooked the right temp but served cold and had to be sent back! Mine was stringy but I ate it. I'm convinced they've changed suppliers. Worse yet, and the challenge so many businesses could remedy, was watching the the manager walk around the restaurant doing nothing. Our server apologized multiple times without our having said anything. Thought the manager standing next to our table would have the chance to explain the issue. Oh well. No shortage of steakhouses in town!
- n3:coolReviews
-
0
- rev:reviewer
-
n7:R_GevUmnYpgFwnL7PXnDaA