A question about using an improved convolutional neural network for sentiment classification

By -

For the changes to CNN proposed in the paper "Detecting Dependency-Related Sentiment Features for Aspect-level Sentiment Classification": After extracting the features in the convolutional layer, the features are multiplied by the dependency weights proposed in the text to obtain the weighted features, and then input to the pooling Floor.

Dependency weighting is a real value that quantitatively measures the dependency-relatedness between a word and the aspect term in a sentence.

Dependency weighting of each word is calculated by inputting syntactic distance between it and the aspect term to some decreasing functions. The shortest path algorithms can calculate syntactic distances between all word pairs. On the dependency parse tree, words with smaller syntactic distance to the aspect term are more closely related than the other words. The dependency parse tree can be annotated manually according to dependency grammar or created automatically by parsers.

enter image description here

I would like to ask you, if I use a data set with aspect labels now, how do I write code to calculate the syntactic distance when I enter a sentence? That is how to apply this shortest path algorithm. (I have learned that one is to create a dependency parse tree first, and then use the shortest path algorithm. But I haven't figured out how to write code to create a dependency parse tree)



from Recent Questions - Stack Overflow https://ift.tt/3nEcaiX
https://ift.tt/3BoY0qR

Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk.
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch").build();     TransportClient client = new P
Read more