[ 
https://issues.apache.org/jira/browse/OPENNLP-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mondher Bouazizi updated OPENNLP-757:
-------------------------------------
    Attachment: supervised.patch

I am using a connector in Eclipse which is Subversive - SVN Team Provider.
However, I tried again, this time using turtoise. Please find attached the new 
patch.
I also removed the training files. The files are collected from the Senseval-3 
website [1]. There is no information regarding whether the dataset is licensed 
or not.
____________
[1] http://www.senseval.org/senseval3/data.html

> Supervised WSD techniques
> -------------------------
>
>                 Key: OPENNLP-757
>                 URL: https://issues.apache.org/jira/browse/OPENNLP-757
>             Project: OpenNLP
>          Issue Type: New Feature
>          Components: Machine Learning, POS Tagger, Sentence Detector, Stemmer
>            Reporter: Mondher Bouazizi
>              Labels: gsoc, gsoc2015, java, nlp, wsd
>         Attachments: opennlp-wsd-supervised.patch, sup.patch, supervised.patch
>
>
> The objective of Word Sense Disambiguation (WSD) is to determine which sense 
> of a word is meant in a particular context. Therefore, WSD is a 
> classification task, where the classes are the different senses of the 
> ambiguous word.
> Different techniques are proposed in the academic literature, which fall 
> mainly into two categories: Supervised and Unsupervised.
> For this component, we focus on supervised techniques: these approaches use 
> machine-learning techniques to learn a classifier from labeled training sets.
> The object of this project is to create a WSD solution (for English) that 
> implements some supervised techniques. For example:
> - Decision Lists
> - Decision Trees
> - Naive Bayes
> - Neural Networks
> - Exemplar-Based or Instance-Based Learning
> - Support Vector Machines
> - Ensemble Methods
> - Semi-supervised Disambiguation
> - Etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to