WordNet - RTE Users
Jump to navigation
Jump to search
When not otherwise specified, the data about usage of the resource have been provided by participants theirselves.
| Participants* | Campaign | Version | Specific usage description | Evalutations / Comments |
|---|---|---|---|---|
| VENSES | RTE3 | 3.0 | Semantic relation between words | No evaluation of the resource |
| AUEB | RTE3 | 2.1 | Synonymy resolution | Replacing the words of H with their synonyms in T: on RTE3 data sets 2% improvement |
| Boeing | RTE4 | 2.0 | Semantic relation between words | No formal evaluation. Plays a role in most entailments found. |
| DFKI | RTE4 | 3.0 | Semantic relation between words | No separate evaluation |
| CERES | RTE4 | 3.0 | Hypernyms, antonyms, indexWords (N,V,Adj,Adv) | Used, but no evaluation performed |
| Cambridge | RTE4 | 3.0 | Meaning postulates from WordNet noun hyponymy, e.g. forall x: cat(x) -> animal(x) | No systematic evaluation |
| BIU | RTE4 | 3.0 | Derived on the fly lexical entailment rules, using synonyms, hypernyms (up to two levels) and derivations. Also used as part of our novel lexical-syntactic resource | 0.8% improvement in ablation test on RTE-4. Potential contribution is higher since this resource partially overlaps with the novel lexical-syntactic rule base |
| FbkIrst | RTE4 | 3.0 | Lexical similarity | No precise evaluation of the resource has been carried out. In our second run we used a combined system (EDITSneg + EDITSallbutneg), and we had an improvement of 0.6% in accuracy with respect to the first run in which only EDITSneg was used. EDITSallbutneg exploits lexical similarity (WordNet similarity), but we can’t affirm with precision that the improvement is due only to the use of WordNet |
| AUEB | RTE4 | Data taken from the RTE4 proceedings. Participants are recommended to add further information. | ||
| DLSIUAES | RTE4 | Data taken from the RTE4 proceedings. Participants are recommended to add further information. | ||
| EMORY | RTE4 | Data taken from the RTE4 proceedings. Participants are recommended to add further information. | ||
| FSC | RTE4 | Data taken from the RTE4 proceedings. Participants are recommended to add further information. | ||
| IIT | RTE4 | Data taken from the RTE4 proceedings. Participants are recommended to add further information. | ||
| IPD | RTE4 | Data taken from the RTE4 proceedings. Participants are recommended to add further information. | ||
| OAQA | RTE4 | Data taken from the RTE4 proceedings. Participants are recommended to add further information. | ||
| QUANTA | RTE4 | Data taken from the RTE4 proceedings. Participants are recommended to add further information. | ||
| SAGAN | RTE4 | Data taken from the RTE4 proceedings. Participants are recommended to add further information. | ||
| Stanford | RTE4 | Data taken from the RTE4 proceedings. Participants are recommended to add further information. | ||
| UAIC | RTE4 | Data taken from the RTE4 proceedings. Participants are recommended to add further information. | ||
| UMD | RTE4 | Data taken from the RTE4 proceedings. Participants are recommended to add further information. | ||
| UNED | RTE4 | Data taken from the RTE4 proceedings. Participants are recommended to add further information. | ||
| Uoeltg | RTE4 | Data taken from the RTE4 proceedings. Participants are recommended to add further information. | ||
| UPC | RTE4 | Data taken from the RTE4 proceedings. Participants are recommended to add further information. | ||
| New user | Participants are encouraged to contribute. |
| Total: 23 |
|---|
[*] For further information about participants, click here: RTE Challenges - Data about participants
Return to RTE Knowledge Resources