The best way to combine en_coreference_web_trf
with en_core_web_trf
in a single pipeline
#12302
Replies: 2 comments 8 replies
-
Thanks! 🤗 Sorry that this has been inconvenient. We appreciate reports of use-cases like yours to help us establish what functionality is needed when we pull the For now, if you want to combine these models, you can use the function
Which should give you sensible results for all components. |
Beta Was this translation helpful? Give feedback.
-
I'm printing the POS and dependency relation using the command you used above i.e.
but i'm getting output to be
Here's the whole code for reference
I'm using only "en_coreference_web_trf" here. Also, it is printing the coref_clusters from doc.spans but not pos and dep. |
Beta Was this translation helpful? Give feedback.
-
Hi,
first of all, thanks for the awesome work with
spacy
! Now, I am working on an application which depends on both super accurate and meaningful linguistic annotations (.pos
and.dep
) provided byen_core_web_trf
model (which works really well for my usecase) as well as coreference resolution for which I want to use the newen_coreference_web_trf
model.However, it seems both of them use different transformer pipeline components and when I try to run
coref
component based ontransformer
fromen_core_web_trf
the results are significantly worse. Similarily, when I usetransformer
fromen_coreference_web_trf
the linguistic annotation produced byen_core_web_trf
are really meaningless and useless and do not make any sense.Is there any way I can have the best of both worlds? Below is an example of a the problem.
Case I: using transformer from
en_core_web_trf
Case II: using transformer from
en_coreference_web_trf
Beta Was this translation helpful? Give feedback.
All reactions