as in #71 mentioned the Recognition of nested Coref Chains is moved to the loadtext route.
It however doesnt work yet, because the old nestedChains Recognition was able to access the mentionIDs that are given from the DB to mark found nested Mentions.
I still need some time to find a way to get/set them before/during the text upload to the DB.
The use-case for nestedChains is the user-selection/hovering of coref Chains. If the user is selecting a mention that is in another the inner Mention should be selected and not the outer.
as in #71 mentioned the Recognition of nested Coref Chains is moved to the loadtext route.
It however doesnt work yet, because the old nestedChains Recognition was able to access the mentionIDs that are given from the DB to mark found nested Mentions.
I still need some time to find a way to get/set them before/during the text upload to the DB.
The use-case for nestedChains is the user-selection/hovering of coref Chains. If the user is selecting a mention that is in another the inner Mention should be selected and not the outer.