What are the causes of predicting weird char span of entities? about tplinker-joint-extraction HOT 2 CLOSED

I had never come into this situation before. Maybe there is something wrong with the offset mapping list, you could check out whether there is a problem with predicted token spans. If not, the problem might come from the mapping progress from token spans to char spans. You need to debug by yourself.

from tplinker-joint-extraction.

Hi mate, I haven't dived into it that you mentioned yet. I've found the issue is highly related to max_seq_len; the smaller max_seq_len is, the more entities with those outranged spans appear. The issue has been solved since I adjust the value of max_seq_len to 512 (max input len for BERT), which is the default value that you set.

However, there are still some entities with empty spans. I'll check it out few days later when I'm free.

Many thanks

from tplinker-joint-extraction.