Hostname: page-component-74656f9884-c52kr Total loading time: 0 Render date: 2026-11-07T20:00:38.097Z Has data issue: false hasContentIssue false

Unsupervised acquisition of entailment relations from the Web

Published online by Cambridge University Press:  30 July 2013

IDAN SZPEKTOR
Affiliation:
Yahoo! Research, Haifa, Israel e-mail: idan@yahoo-inc.com
HRISTO TANEV
Affiliation:
JRC, Ispra, Italy e-mail: htanev@gmail.com
IDO DAGAN
Affiliation:
Department of Computer Science, Bar-Ilan University, Ramat Gan, Israel e-mail: dagan@cs.biu.ac.il
BONAVENTURA COPPOLA
Affiliation:
IBM Thomas J. Watson Research Center, Yorktown Heights, NY e-mail: bcoppola@us.ibm.com
MILEN KOUYLEKOV
Affiliation:
CELI s.r.l., Torino, Italy e-mail: kouylekov@celi.it
Rights & Permissions [Opens in a new window]

Abstract

Entailment recognition is a primary generic task in natural language inference, whose focus is to detect whether the meaning of one expression can be inferred from the meaning of the other. Accordingly, many NLP applications would benefit from high coverage knowledgebases of paraphrases and entailment rules. To this end, learning such knowledgebases from the Web is especially appealing due to its huge size as well as its highly heterogeneous content, allowing for a more scalable rule extraction of various domains. However, the scalability of state-of-the-art entailment rule acquisition approaches from the Web is still limited. We present a fully unsupervised learning algorithm for Web-based extraction of entailment relations. We focus on increased scalability and generality with respect to prior work, with the potential of a large-scale Web-based knowledgebase. Our algorithm takes as its input a lexical–syntactic template and searches the Web for syntactic templates that participate in an entailment relation with the input template. Experiments show promising results, achieving performance similar to a state-of-the-art unsupervised algorithm, operating over an offline corpus, but with the benefit of learning rules for different domains with no additional effort.

Information

Type
Articles
Copyright
Copyright © Cambridge University Press 2013 
Figure 0

Table 1. Examples of correct entailment relations learned by the TEASE algorithm: each learned template participates in an entailment relation with the input verb

Figure 1

Table 2. Example for feature vectors, one for each slot, constructed by the DIRT algorithm for two templates (scores are omitted for brevity). A significant amount of features are shared between the two templates (in bold), indicating their semantic similarity

Figure 2

Fig. 1. The TEASE algorithm outline.

Figure 3

Fig. 2. The ASE algorithm outline.

Figure 4

Table 3. Examples of correct characteristic anchor-sets learned for several input templates. X and Y are the slot anchors. C1 is a context anchor

Figure 5

Table 4. Examples of incorrect characteristic anchor-sets extracted by the ASE phase

Figure 6

Fig. 3. Two parse trees and their CGR. The indexes on the nodes, e.g. |6, denote vertex labels or sets of labels. The index pairs on the edges, e.g. (1, 2)(4, 6), denote edge labels or sets of labels. Nodes and edges in bold indicate the LGMG template within the CGR graph.

Figure 7

Fig. 4. Two parse trees and their CGR, where the LGMG template (bolded nodes and edges) in the CGR graph is not a path between the two variables.

Figure 8

Table 5. Examples of correct templates learned for several input templates

Figure 9

Table 6. Rule evaluation examples and their judgment

Figure 10

Table 7. Examples for disagreement between the two judges

Figure 11

Table 8. Average Precision (P) and Yield (Y) at the rule and template levels

Figure 12

Table 9. The top 18 correct templates learned by TEASE for‘X interact with Y’

Figure 13

Table 10. The potential Recall of TEASE in terms of distinct pairs of interacting proteins (out of 418 annotated pairs)

Figure 14

Table 11. Distribution of reasons for learning incorrect templates by TEASE

Figure 15

Table 12. Correct templates that were learned by TEASE and cannot be extracted from WordNet