inception icon indicating copy to clipboard operation
inception copied to clipboard

Coreference Chain Cross-linking mistake correction

Open XiaoyanYangAlice opened this issue 5 months ago • 1 comments

Is your feature request related to a problem? Please describe. When coreference chains for two distinct entities (e.g., "Will" and "Nico") become completely cross-linked/fused, the process of separating them is extremely difficult and prone to data loss due to unexpected undo/redo behavior.

Describe the solution you'd like Currently, we tried to manually separate the fused chains by deleting individual "mislink" (links that incorrectly connect mentions from the two entities). However, deleting mislink does not cleanly separate the chains into their original distinct entities; instead, it breaks the large fused chain into smaller segments that still contain mixed mentions.

Observe that deleting mislink does not cleanly separate the chains into their original distinct entities; instead, it breaks the large fused chain.

Is there a solution to better solve this mistake rather than deleting all the coreference chain and redo it?

Describe alternatives you've considered Last week I used WebAnno 3 Version exported the project, that's when the mistake has not been made, is there any possible way to go back to this version?

Additional context

XiaoyanYangAlice avatar Jul 06 '25 07:07 XiaoyanYangAlice

Wrt going back to the version from the exported project: there is currently no easy way to override the annotations of a specific annotator. In theory, you could do it be importing your project again into INCEpTION, then enabling the remote API of INCEpTION, downloading the annotations from your projectB/document/annotator and uploading it again via the remote API to the projectA/document/annotator.

https://inception-project.github.io/releases/37.1/docs/admin-guide.html#sect_remote_api

Coreference chain support has various problems. I have already considered degrading it to experimental status and/or potentially even removing it entirely in favor of just using spans and relations. Or maybe an opportunity comes up to work on it...

reckart avatar Jul 10 '25 18:07 reckart