Dependency conflict between radboud-el and xrenner about elevant HOT 4 CLOSED

Thanks for reporting it! I will look into it, but in the meantime, if you are not using coreference resolution, the best solution is probably to remove xrenner from the requirements entirely.

from elevant.

Thank you! Leaving out xrenner did work for now. However, I would like to have the option of using coref in the future, though it's not critical right now. Is there a chance that neuralcoref might be replaced with something like https://github.com/shon-otmazgin/fastcoref, or that it could be included as an option? Fastcoref seems to be pretty standard these days, and seems to be actively maintained.

from elevant.

That looks really good at first glance, thanks for the link. I'll definitely look at adding support for it in ELEVANT.

from elevant.

I removed support for xrenner and added support for fastcoref. You can test it e.g. in combination with ReFinED on our benchmark Wiki-Fair which contains coreference ground truth mentions:

python3 link_benchmark_entities.py refined.fastcoref -l refined -coref fastcoref -b wiki-fair

Note that you cannot use a coreference linker in isolation (without specifying an entity linker), since ELEVANT evaluates the linked entities, not the coreference clusters themselves.

from elevant.