Attachment Ambiguity—or—when is the gyudon cheap?
Every day on the way to work I walk by a fine establishment known as [[Yoshinoya]] (吉野家), Japan’s largest gyudon (牛丼) chain restaurant. For those of you whose lives have yet to be graced by [[gyudon]], it’s a bowl of rice topped with beef and onions stewed in a sweet-savory soy-based sauce. Loving gyudon and being a cheapskate, I naturally noticed the recent 50 yen off gyudon promotion at Yoshinoya. The above photo is a photo of part of that sign.
| Part of this sign, though, made me think about our new Ubiquity parser. In particular, it was the attachment ambiguity in the end date of the promotion. The text in the photo above literally is “April 15th (Wed.) 8PM until”. (Note that Japanese is a strongly head-final language, and that the “until” is a postposition.) There are two possible readings for this expression, as illustrated by the two [[principle of compositionality | composition]] trees below. |
The first tree, on the left, represents the reading “until (April 15th 8PM)”, while the second represents two arguments: “on April 15th” and “until 8PM”. In other words, in the first reading, the promotion begins at some earlier date and extends until April 15th at 8PM while, in the second reading, the promotion is one day only, on April 15th, until 8pm. Such syntactic ambiguities are called “attachment ambiguities” in linguistics as it is an ambiguity of where different arguments “attach” in a tree representation.
This attachment ambiguity was possible because there was no clear marker on “April 15th,” which may have disambiguated it as “on April 15th”. In fact, in many languages this time position argument comes with no case marker or preposition, or it’s optional, making parsing for them difficult. If such a sentence is entered with spaces, the Ubiquity Parser: The Next Generation would try a parse where “8PM” is the “until” or goal argument and “April 15th” is an object argument, but it will only check its noun type, not put it in the correct semantic role (position). Perhaps this is something to think about in the future.
These types of situations will surely come up as we continue work on the Ubiquity parser, making it essential to look at different languages. Are there certain kinds of arguments in your language that do not have any word-external markers such as case or prepositions/postpositions?