From ab27431a21f230547b1b71ab140847fc6fca91a1 Mon Sep 17 00:00:00 2001 From: James Ravenscroft Date: Fri, 31 Dec 2021 16:16:12 +0000 Subject: [PATCH] correct cd2cr thing --- .../content/posts/2021/12/2021-12-31-retrospective/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/brainsteam/content/posts/2021/12/2021-12-31-retrospective/index.md b/brainsteam/content/posts/2021/12/2021-12-31-retrospective/index.md index b2403ff..b4f6bb0 100644 --- a/brainsteam/content/posts/2021/12/2021-12-31-retrospective/index.md +++ b/brainsteam/content/posts/2021/12/2021-12-31-retrospective/index.md @@ -29,7 +29,7 @@ My biggest personal achievement this year was getting married. My wife and I hav ## 📔 Publishing at EACL -In January I found out that my paper [$CD^2CR$: Co-reference Resolution Across Documents](https://arxiv.org/abs/2101.12637) and Domains had been accepted at EACL2021. +In January I found out that my paper [CD2CR: Co-reference Resolution Across Documents and Domains](https://arxiv.org/abs/2101.12637) had been accepted at EACL2021. Co-reference resolution is basically knowing that the *he* in "James is an IT professional. *He* lives in England" refers to James. The whole premise of my work was that it allows you to resolve co-references between different types of documents. For example if a news article says "new species of dinosaur discovered" and it links to a scientific paper that says "we discovered Triceratops horridus in a fossil on the coast of Dorset" then the task would be to know that "dinosaur" and "Triceratops horridus" refer to the same thing.