-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hierarchical sentiment classifier, single feature classification, erroneous probabilities? #27
Comments
For some reason, when classifying a document that consists only of one feature, the hierarchical classifier only labels the document as neutral or positive, even when the confidence values are less than 0.5. I'm still not sure why this is the case, however I am addressing the issue for the part of the web interface that shows the influence of each of the individual features that make up the query by just using the conditional probability of the feature across the labels instead of trying to classify it. In the mean time, this addresses issue gh-27.
Now, using conditional probabilities only (instead of trying to classify each feature as its own document):
Perhaps by the prior probabilities skew the overall classification so much that just a single feature isn't capable of overcoming the priors. Now that I think about it, why are we throwing away the confidence value from the classification process, and re-calculating it from the conditionals? Which is the correct approach? |
When we use the original confidence value from the classification process, we get:
Why are there only two unique confidence values across all features? Shouldn't the individual conditional probabilities cause at least some variation? |
Part of the web interface is supposed to show how each feature would be classified if it was a document of length one. Why does the hierarchical sentiment classifier only label these individual features as either
neutral
orpositive
, even when the confidence value is less than 0.5?As an example:
Current hash: 5fd9baa
The text was updated successfully, but these errors were encountered: