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 |
|---|
| n5 | 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/ |
| n7 | http://data.yelp.com/Business/id/ |
| rev | http://purl.org/stuff/rev# |
| xsdh | http://www.w3.org/2001/XMLSchema# |
| n4 | http://data.yelp.com/User/id/ |
Statements
- Subject Item
- n2:ERd9vdCSwoYo4c0NsRLNtQ
- rdf:type
-
rev:Review
- schema:dateCreated
-
2015-06-29T00:00:00
- schema:itemReviewed
-
n7:_XVHWZ_epQZkDxg1alyD-g
- n5:funnyReviews
-
0
- rev:rating
-
3
- n5:usefulReviews
-
3
- rev:text
-
Four of us dined here for lunch this afternoon. including the appetizer it was around $120.00. This was 2 steak specials, smothered chicken, and a salmon dish (entrees included salad and a side). The food quality was all good, except for the onion appetizer which was dripping with grease and harder to eat then you're standard steakhouse onion plate. Mashed potatoes were good... sautéed muchrooms and onions were good... two steak eaters were happy (though not over the moon). Smothered chicken was flavorful and salmon was "pretty okay". And our waiter was a nice guy, cracked a few jokes, and had fun with us. So in the end it's pretty much the definition of a 3 out of 5. It wasn't bad really. It just wasn't anything too special. If I had a choice, I'd probably do Longhorn instead - especially based on the price.
- n5:coolReviews
-
1
- rev:reviewer
-
n4:dl8X1gctvSmJzUKwPj50Vw