Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

No valency instances from Apertium Russian parser results #953

Closed
myrix opened this issue Mar 21, 2023 · 1 comment
Closed

No valency instances from Apertium Russian parser results #953

myrix opened this issue Mar 21, 2023 · 1 comment
Labels
backend bug is related to backend enhancement this label means that resolving the issue would improve some part of the system

Comments

@myrix
Copy link
Contributor

myrix commented Mar 21, 2023

On http://lingvodoc.ispras.ru/valency there's no instances from the http://lingvodoc.ispras.ru/dictionary/6236/1709/perspective/6236/1712/view corpus.

The problem is non-standard VBLEX and VBSER verb markers of the Apertium Russian parser,
image image,
incompatible with Lingvodoc's valency instance code which understands only V.

We should upgrade the code so that VBLEX- and VBSER-marked verbs are also recognized.

@myrix myrix added enhancement this label means that resolving the issue would improve some part of the system backend bug is related to backend labels Mar 21, 2023
@myrix myrix self-assigned this Mar 21, 2023
@myrix
Copy link
Contributor Author

myrix commented Mar 21, 2023

Implemented, now we can have instances from this corpus.

To ensure instance generation, it's better to create new entries, re-upload and re-parse documents, and then disambiguate two or three words in each new parser result. Then new instances would be generated after selecting the corpus at http://lingvodoc.ispras.ru/valency and clicking 'Update valency data' button.

We probably should make valency data updating better, in particular, finish #775 and and think about how we should do it in cases like this, when we change the algorithm and should re-parse some data, when data does not change.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
backend bug is related to backend enhancement this label means that resolving the issue would improve some part of the system
Projects
None yet
Development

No branches or pull requests

1 participant