Live data from Hacker News

Agglutinative Language

en.wikipedia.org

11–20 of 32 posts

Re: Agglutinative Language

#11

Turkish is probably strict enough to be used as a programming language. The only downside is that its vocabulary is utterly alien for most speakers of Latin/Anglo-Saxon languages aside from some borrowed words from French and Arabic.

[deleted]

Re: Agglutinative Language

#12

Can someone here explain this in an easier to understand way? This was a bit too dense for my understanding...

The smallest unit in language that has meaning is called a morpheme. Some languages use relatively few morphemes-per-word like English: for example, the word "cats" can be broken into two morphemes -- "cat" and "-s". "Two" can't be broken down any further, so it has a 1-to-1 mapping between morphemes and words.

Other languages use a lot of morphemes-per-word. One strategy to create words from morphemes is called agglutination (meaning to glue things together). An agglutinative language takes all the morphemes that are going to go into a word, and with minimal or no changes, glues them together to form a word.

For example, the Yupik word "tuntussuqatarniksaitengqiggtuq" means "He had not yet said again that he was going to hunt reindeer". It is formed by taking the following morphemes and agglutinating them:

"tuntu-ssur-qatar-ni-ksaite-ngqiggte-uq"

Re: Agglutinative Language

#13

Can someone here explain this in an easier to understand way? This was a bit too dense for my understanding...

Simply put: a lot of grammar is based on appending to words. E.g. the Turkish word for book is Kitab (shared by a bunch of other middle eastern languages too). My Book is Kitabim. Your book is Kitabsin. (Note last example is vastly simplified, a proper Turkish speaker should correct it) It allows for a lot of really short sentences; here's a nonsensical example: His book is on fire - kitabı yanıyor. The word endings…

These are actually mostly wrong

- Book = kitap, not kitab

- My book = kitabım, not kitabim

- Your book = kitabın, not kitabsin

Re: Agglutinative Language

#14
I often wonder how much of a head start the isolating nature of English gave for computing. It allowed ignoring a lot of inflectional and agglutinative complexity.

Concretely I mean it's very easy to generate text using sentence templates. Just plug in words and it works out. "The $process_name has completed running." "Like $username's comment" "Ban $username".

Relatedly, I think focusing NLP efforts on English masks a lot of interesting phenomena, because English text already comes in a reasonably tokenized, chunked up and pre-digested, easy to handle form. For example speech recognition systems started out with closed vocabularies, with larger and larger numbers of words, and even in their toy forms you could recognize some proper English sentences. To do that in Hungarian for example, the "upfront costs" to a "somewhat usable" system are much higher, because closed vocabulary doesn't get you anywhere. (Similarly, learning basic English is very easy, you can build 100% correct sentences on day 1, you learn "I", "you", "see" and "hear" and can say "I see" and "You see" and "I see you" and "I hear Peter" which are all 100% correct. In Hungarian these are "nézek", "nézel", "nézlek", "hallom Pétert" requiring learning several suffixes and vowel harmony and definite/indefinite conjugation. The learning curve till your first 100% correct 3-5 word sentences is just steeper.)

I don't mean it's impossible to handle agglutinative languages in NLP, I just mean the "minimum viable model" is much simpler and attainable for English, which on the one hand was able to kickstart and propel the early research phases and on the other hand perhaps fueled a bit too much optimism.

English can seem very well structured and it can tempt one to think of language in a very symbolic, within-the-box, rule-based way. In terms of syntax trees, sets of valid sentences etc, instead of "fuzzy probabilistic mess" that it really is. Surely, the syntax tree, generative grammar approach (Chomsky and others) gave us a lot of computer science, but this kind of "clean" and pure symbolic parsing doesn't seem to drive today's NLP progress.

In summary, I wonder how linguistics and especially computational linguistics and NLP would have evolved in a non-Anglo culture, e.g. Slavic or Hungarian.

Re: Agglutinative Language

#15

Can someone here explain this in an easier to understand way? This was a bit too dense for my understanding...

The article notes that in some languages it is possible to form sentences by chaining appendixes to them.

An example in Finnish:

- jousta (normal form of the verb run)

- juoksen (I run)

- juoksentelen (I run around)

- juoksentelisinkohan (I wonder should I run around)

- juostaankohammekohaan (I wonder do we run)

The two later forms are very rarely used, and I have no idea whether the last form is even correct. I have some friends who insist on talking like this. Usually, people express the same things with more words, such as juoksentelisinkohan is equivalent to about:

- Mietin ., että. pitäisikö. minun. juosta. ympäriinsä.

- I wonder., that. should. my (in this context, me). run. around.

The . are to separate the words.

Yet, it would be perfectly fine to just append a question mark to juoksentelisinkohan or juostaankohammekohaan and it would be a one-word sentence. An interesting remark is that in practice the question mark is redundant in both cases, as the -ko- part in the words reduces the only interpretation of the word to be a question.

I have absolutely no idea how would one formalize all this.

Re: Agglutinative Language

#16

Earlier quoted context omitted.

Simply put: a lot of grammar is based on appending to words. E.g. the Turkish word for book is Kitab (shared by a bunch of other middle eastern languages too). My Book is Kitabim. Your book is Kitabsin. (Note last example is vastly simplified, a proper Turkish speaker should correct it) It allows for a lot of really short sentences; here's a nonsensical example: His book is on fire - kitabı yanıyor. The word endings…

These are actually mostly wrong - Book = kitap, not kitab - My book = kitabım, not kitabim - Your book = kitabın, not kitabsin

The i is due to using English keyboard, it's a bit tricky to type the proper i without autocompletion.

Re: Agglutinative Language

#18

I often wonder how much of a head start the isolating nature of English gave for computing. It allowed ignoring a lot of inflectional and agglutinative complexity. Concretely I mean it's very easy to generate text using sentence templates. Just plug in words and it works out. "The $process_name has completed running." "Like $username's comment" "Ban $username". Relatedly, I think focusing NLP efforts on English masks…

Being able to encode it reasonably in 5 bits and comfortably in 6 (adding case and a few last nice symbols) was helpful too.

Re: Agglutinative Language

#19

Can someone here explain this in an easier to understand way? This was a bit too dense for my understanding...

Agglutinative just means you glue (the -glu- refers to this) pieces (suffixes) at the end of words to express lots of things. This exists in English as well, but in restricted forms. For example blue+ish, quick+ly, blue+ness, look+ed. In an agglutinative language, this is how most of the things are expressed. For example a totally normal Hungarian word is: szolgáltatásaiért = szolgá+l+tat+ás+a+i+ért = for his/her/its…

More on this:

szolga = servant

+ l = verb-forming suffix [1]

+ tat = causative suffix [2]

+ ás = gerund-forming suffix, makes a verbal noun from a verb [3]

+ ai = marker for plural possession [4]

+ ért = causal-final suffix, denotes the reason for the action [5]

These suffixes are morphemes you can (with some simple rules) just add to words to achieve the corresponding change in meaning. In CS terms, they're functions that take the input word and make a new one. Each one of the above, used somewhere else:

winter -> to spend the winter: tél + l -> telel

to read -> to make them read: olvas + tat -> olvastat

to read -> the reading: olvas + ás -> olvasás

house -> his houses: ház + ai -> házai

house -> because of, affecting the house: ház + ért -> házért

[1] https://en.wiktionary.org/wiki/-l#Hungarian [2] https://en.wiktionary.org/wiki/-tat#Hungarian [3] https://en.wiktionary.org/wiki/-%C3%A1s#Hungarian [4] https://en.wiktionary.org/wiki/-ai#Hungarian [5] https://en.wiktionary.org/wiki/-%C3%A9rt

Re: Agglutinative Language

#20

Earlier quoted context omitted.

It's actually quite a bit easier to learn since it has few false friends with Latin languages. I often thought search engines written by English speakers focused on bags of words can't work very well in Turkish though?

Not only search, but also autocorrect. Turkish autocorrect on iOS is a flaming disaster even after a decade. Here’s a real (if unlikely) word in Turkish and how this whole agglutination business works: https://twitter.com/languagecrawler/status/62385880386859827... I don’t blame Apple though - it might actually be just impossible to do Turkish autocorrect in the same way English autocorrect works, because the beginni…

Seems like you're talking about autocompletion, not autocorrect. In autocorrect you have completed the word, hit space and then the software fixes your typos. In autocomplete you get a list of suggested words while typing and you can tap them if your intended word is shown.
Post reply on HN