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

Statements

Subject Item
n2:oR_fc2Mz_67RKysk9agJ7Q
rdf:type
rev:Review
schema:dateCreated
2011-07-22T00:00:00
schema:itemReviewed
n7:Tf1zl5szY-u8C3J0AcygDQ
n4:funnyReviews
2
rev:rating
1
n4:usefulReviews
2
rev:text
Will never go back to this resto. Menu and Pics deceive customers. Pic of menu posted mention it is good for 2. Price is for one person. If you don't check the fine print you will think the price is for 2. Many have been shocked liked they were charged double. I don't understand the reason for the price per person thing. This is the practice in Korean restaurants. Most of them even require you to order 2 main courses when some of their food is good for 2 already. If food is good for 2 they should post the price correctly. It is not worth at all for another reason. The raw beef to be cooked shabu shabu style does not resemble how much it is in the picture. We actually counted 59 pieces of beef in the menu picture. Actual number of pieces was 22. I call this deception. It would have been acceptable if the difference was minimal. Furthermore, the first server who barely speaks English confirmed to us that the price posted is for 2. Then the 2nd server came around to tell us that the price was to be double because posted price was for one person. We ended up paying so much for little. Will never go back to this resto.
n4:coolReviews
0
rev:reviewer
n5:XUtrdZW2ePLTUyiSR8o3IQ