{"id":176,"date":"2019-03-12T14:01:00","date_gmt":"2019-03-12T13:01:00","guid":{"rendered":"https:\/\/daniel.liljeberg.io\/?p=176"},"modified":"2021-04-01T22:02:08","modified_gmt":"2021-04-01T20:02:08","slug":"language-classification-using-machine-learning-in-php","status":"publish","type":"post","link":"https:\/\/daniel.liljeberg.io\/sv\/2019\/03\/12\/language-classification-using-machine-learning-in-php\/","title":{"rendered":"Language classification using Machine Learning in PHP"},"content":{"rendered":"\n

So, like many of us I decided to dabble a bit in Machine Learning (ML) and took a short course in the subject. One of the parts of the course was to create a small ML project. I wanted to try and make something practical out of it though and looked around at work to see what potential issues I could try to solve using ML.<\/p>\n\n\n\n

Like any large company we do business basically over the entire globe. Business generates support requests and my first idea was to estimate the expected time a case would take to solve based on different parameters of the case. This could then be used to allocate staffing, identify specific types of cases that would benefit from implementing better solutions etc. Having limited time though and not access to enough data about the cases I was forced to abandon this since the only thing I was able to easily get at the time was basically the subject line, email of the sender and a few other pieces. Not enough to generate a near enough robust module for me to trust the estimates it would produce.<\/p>\n\n\n\n

So I looked at it again, what other “problems” do our support tickets present? Well, since many of the support requests are sent to the initial email address that address receives support requests in all manner of languages. Sure, we can manually handle that and re-assign to support personnel in the country in question or ask everyone that submits a request to re-submit in English. But one takes time and adds the risk of requests being left for a time before being re-assigned and the other had already been tested without much success. Partly because people traditionally had already been used to receiving support in their native language and just because our company grew it made little sense that this would go away.<\/p>\n\n\n\n

So, what if we could identify the language and then use that to redirect the request to a group of people who know the language in question and can provide support in that language?<\/p>\n\n\n\n

\"PHP-ML\"<\/figure><\/div>\n\n\n\n

Many ML examples are written in, Python and so was a major part of the course. But I decided to see if I could write my project in PHP. I do most of my development using C++ but when it comes to web-development and scripting I have used PHP for a long time. So I wanted to see how easy it would be to use PHP and it would also enable me to easily use what I created in my own PHP projects. A quick look around and I found PHP-ML<\/a>. A Machine Learning library for PHP. It lacks some of the stuff you find in Scikit-learn for instance, but it seems to be in active development and adding features so things like Convolutional Neural Networks<\/em> that are not in the library today will probably make it in with time.<\/p>\n\n\n\n

Choosing classifier<\/h2>\n\n\n\n

Since I would be working with text and the goal was to classify <\/em>which language a given text belonged to a classifier like Naive Bayes or SVC felt like the best options.<\/p>\n\n\n\n

In order to facilitate helping new going down the ML rabbit hole Scikit-learn.org has a good map for choosing the correct classifier and that affirmed my initial pick.<\/p>\n\n\n\n

\"scikit-learn<\/figure>\n\n\n\n

I decided to test both Naive Bayes and SVC since I felt Naive Bayes would be faster to train, but SVC might result in better accuracy.<\/p>\n\n\n\n

Data collection and pre-processing<\/h2>\n\n\n\n

The first obstacle in creating any ML model is to get the data to train on. If I would like to be able to classify a set of languages I clearly needed sample sentences from these languages to train on. But collecting a large set of sentences in each language would be quite time consuming and time was something I didn’t have, not to mention I didn’t speak the majority of these languages. I decided to go another, more rudimentary route. Instead of manually translating a list of sentences or finding unique lists of sentences I decided to let Google do the job for me.<\/p>\n\n\n\n

I started by collecting a set of sentences in English, using that as my base sample set. I acquired these were basically by Googling \u201cEnglish sentences for kids\u201d, \u201cEnglish sentences for adults\u201d<\/em> etc and compiling a list of sentences that I could use as my base. The first issue I found was that many of the sentences included very uniquely English sayings, which could probably cause issues since they are not to be taken literally. But I cleaned up the most extreme ones and ended up with 1635 English sentences.<\/p>\n\n\n\n

If this was going into the actual production environment, I would vet the base data-set much more than this since that is the base for everything to come. But for my initial proof-of-concept it would have to do.<\/p>\n\n\n\n

After this, I looked up which languages Google supported.<\/p>\n\n\n\n

$languages = [\n    'af' => 'Afrikaans',\n    'sq' => 'Albanian',\n    'ar' => 'Arabic',\n    'az' => 'Azerbaijani',\n    'eu' => 'Basque',\n    'bn' => 'Bengali',\n    'be' => 'Belarusian',\n    'bg' => 'Bulgarian',\n    'ca' => 'Catalan',\n    'zh-CN' => 'Chinese Simplified',\n    'zh-TW' => 'Chinese Traditional',\n    'hr' => 'Croatian',\n    'cs' => 'Czech',\n    'da' => 'Danish',\n    'nl' => 'Dutch',\n    'en' => 'English',\n    'eo' => 'Esperanto',\n    'et' => 'Estonian',\n    'tl' => 'Filipino',\n    'fi' => 'Finnish',\n    'fr' => 'French',\n    'gl' => 'Galician',\n    'ka' => 'Georgian',\n    'de' => 'German',\n    'el' => 'Greek',\n    'gu' => 'Gujarati',\n    'ht' => 'Haitian Creole',\n    'iw' => 'Hebrew',\n    'hi' => 'Hindi',\n    'hu' => 'Hungarian',\n    'is' => 'Icelandic',\n    'id' => 'Indonesian',\n    'ga' => 'Irish',\n    'it' => 'Italian',\n    'ja' => 'Japanese',\n    'kn' => 'Kannada',\n    'ko' => 'Korean',\n    'la' => 'Latin',\n    'lv' => 'Latvian',\n    'lt' => 'Lithuanian',\n    'mk' => 'Macedonian',\n    'ms' => 'Malay',\n    'mt' => 'Maltese',\n    'no' => 'Norwegian',\n    'fa' => 'Persian',\n    'pl' => 'Polish',\n    'pt' => 'Portuguese',\n    'ro' => 'Romanian',\n    'ru' => 'Russian',\n    'sr' => 'Serbian',\n    'sk' => 'Slovak',\n    'sl' => 'Slovenian',\n    'es' => 'Spanish',\n    'sw' => 'Swahili',\n    'sv' => 'Swedish',\n    'ta' => 'Tamil',\n    'te' => 'Telugu',\n    'th' => 'Thai',\n    'tr' => 'Turkish',\n    'uk' => 'Ukrainian',\n    'ur' => 'Urdu',\n    'vi' => 'Vietnamese',\n    'cy' => 'Welsh',\n    'yi' => 'Yiddish'\n];\n<\/pre>\n\n\n\n
My idea was to make http requests to translate.google.com<\/em> translating the English sentences to each of the other languages. A quick search showed a small library doing exactly what I had in mind already existed so instead of writing it from scratch I decided to use it. https:\/\/github.com\/Stichoza\/google-translate-php<\/a>.<\/p>\n\n\n\n
With it you can simply call something like<\/p>\n\n\n\n
$gt = new GoogleTranslate('en', 'sv');\n$translatedString = $gt->translate(\"Hello World\");\n<\/pre>\n\n\n\n
Making it all come together<\/h3>\n\n\n\n
If this was going into a system or library I would have made the LanguageClassifier a class that encapsulated all the functionality and was easy to use through it’s public interface. But I decided to go with a simple script intended to be used stand alone from a terminal, printing information about what it is doing during execution, for my demonstration.<\/p>\n\n\n\n
I had one file sentences.txt<\/em> that held the English sentences to use as a base. languagedatasset.ser<\/em> which contained a serialized array which looked something like this<\/p>\n\n\n\n
[\n\t'en' => ['xxxxxx' => 'Hello World', 'yyyyyy' => 'I like coffee in the morning'],\n\t'sv' => ['xxxxxx' => 'Goddag v\u00e4rlden' 'yyyyyy' => 'Jag tycker om kaffe p\u00e5 morgonen'],\n\t...\n]<\/pre>\n\n\n\n
where xxxxxx<\/em>, yyyyyy <\/em>etc where checksums of the original English sentence in order to be able to map a sentence to each of he languages. The model trained on the data set would then be stored in a file called model.dat<\/em>.<\/p>\n\n\n\n
The workflow of the script was something like this.<\/p>\n\n\n\n
\/*\n * - If sentences.txt holding base sentences in English exists\n *      - If languagedataset.ser does not exist\n *          - Setup inital english sentences from sentences.txt\n * - If sentences.txt contains new sentences or have removed sentences\n *      - Update english sentences in dataset\n * - For each language\n *      - Check if english sentence exist that is missing for language\n *          - Translate each missing sentence using Google Translate\n *      - Store updated languagedataset.ser\n *\n * - If model.dat already exists or we have to retrain due to changed dataset\n *      - Transform format from languagedataset.ser to an ArrayDataset, train \n *        and check accurcy\n *      - Save model.dat\n * - Else load mode.dat\n * - Classify language of sentences passed\n *\/<\/pre>\n\n\n\n
The result is a script that can take a list of strings and spit out predictions regarding which language each string is written in.<\/p>\n\n\n\n
C:\\tools\\php72\\php.exe E:\\Dropbox\\Projects\\php-ml\\languageClassification.php \"vad heter du?\" \"El toro\" \"Wie viel kostet dieser Computer?\" \"Jutro b\u0119dzie pi\u0119kna pogoda\" \"Domani sar\u00e0 bel tempo\" \"Morgen zal het prachtig weer zijn\" \"Huomenna tulee kaunis s\u00e4\u00e4\" \"Mon ordinateur ne d\u00e9marre pas\" \"min computer starter ikke, og det g\u00f8r mig sk\u00f8r\" \"Goedemorgen, Graag ontvang ik de licentiefiles voor de meters zoals in de bijlage genoemd. User name: foo@bar.com Company: Foo Bar klimaattechniek Customer number: 0123456\"\nDataset up to date\nLoading model... Done\narray(10) {\n  [\"vad heter du?\"]=>\n  string(2) \"sv\"\n  [\"El toro\"]=>\n  string(2) \"es\"\n  [\"Wie viel kostet dieser Computer?\"]=>\n  string(2) \"de\"\n  [\"Jutro b\u0119dzie pi\u0119kna pogoda\"]=>\n  string(2) \"pl\"\n  [\"Domani sar\u00e0 bel tempo\"]=>\n  string(2) \"it\"\n  [\"Morgen zal het prachtig weer zijn\"]=>\n  string(2) \"nl\"\n  [\"Huomenna tulee kaunis s\u00e4\u00e4\"]=>\n  string(2) \"fi\"\n  [\"Mon ordinateur ne d\u00e9marre pas\"]=>\n  string(2) \"fr\"\n  [\"min computer starter ikke, og det g\u00f8r mig sk\u00f8r\"]=>\n  string(2) \"da\"\n  [\"Goedemorgen, Graag ontvang ik de licentiefiles voor de meters zoals in de bijlage genoemd. User name: foo@bar.com Company: Foo Bar klimaattechniek Customer number: 0123456\"]=>\n  string(2) \"nl\"\n}\n\ufeff<\/pre>\n\n\n\n
Test results<\/h2>\n\n\n\n
Due to time constraints, instead of using all the languages that my program supported I decided to go with a subset. This allowed me to run several tests of different sizes of the training set to see how that affected performance.<\/p>\n\n\n\n
I decided to go with eleven different languages and wanted to have a few that were somewhat \u201csimilar\u201d to make it a bit harder for the classifier, so I include Swedish, Norwegian and Danish.<\/p>\n\n\n\n
The complete list of tested languages were:<\/p>\n\n\n\n
Danish, Dutch, English, Finnish, French, German, Italian, Norwegian, Polish, Spanish and Swedish.<\/strong><\/p>\n\n\n\n
The two learning algorithms were run using sample sizes ranging from 100 to 600 sentences. These sentences were all translated into the different languages. So, the sample set of 100 includes 100 sentences for each language. So, the actual sample sizes ranged from 1100 to 6600 sentences.<\/p>\n\n\n\n
Of these, a random selection of 90% were used as the training set and the remaining 10% as the test set. Naive Bayes<\/strong>, as expected, was much faster to train. Time elapsed ofc depends on the hardware used during training, but it\u2019s fair to say that Naive Bayes<\/strong> using 600 sentences per language was almost as fast as SVC<\/strong> at 100 sentences per language. Where Naive Bayes<\/strong> always was a matter of counting seconds while training, SVC<\/strong> quickly moved into counting minutes.<\/p>\n\n\n\n
\"\"<\/figure><\/div>\n\n\n\n
In the table we can see the accuracy results for different amounts of sentences per language used to train on and different variables used for the SVC<\/strong> classifier. Variants of Naive Bayes<\/strong> aren\u2019t currently supported by PHP-ML so only the basic version was tested.<\/p>\n\n\n\n
Since the sentences selected are random each time and the quality of each sentence and its corresponding translations will be better for some than others, variances in reported accuracy is to be expected even for runs with identical settings.<\/p>\n\n\n\n
From the table we can see that Naive Bayes<\/strong> gives a result similar to SVC<\/strong> at much greater training rate, but SVC<\/strong> edges ahead if one tweaks the parameters and takes the win with a maximum score of ~94% accuracy.<\/p>\n\n\n\n
The more sentences used, the longer it takes to train and the larger the resulting model ends up being. For production purpose I would aim for a reasonable middle ground. A large model takes longer to load, can result in more time being needed for predictions etc.<\/p>\n\n\n\n
Source code<\/h3>\n\n\n\n
A script implementing the above ideas can be found here: https:\/\/github.com\/inquam\/php-ml-language-classification<\/a><\/p>\n\t\t\t\n\n\n
\n
Comments<\/h3>\n
 \n
\n\t<\/a>\n\t
\n\t