Skip to content

Handle lexical gaps marked by GAP! or PSEUDOGAP!#57

Merged
goodmami merged 3 commits intomainfrom
gh-45-lexical-gaps
Mar 10, 2025
Merged

Handle lexical gaps marked by GAP! or PSEUDOGAP!#57
goodmami merged 3 commits intomainfrom
gh-45-lexical-gaps

Conversation

@goodmami
Copy link
Copy Markdown
Collaborator

If a synset has a member GAP! or PSEUDOGAP!, that sense is removed and all remaining senses are checked with heuristics to see if they are compositional collocations (the presence of a space or apostrophe for Italian or a space for Hebrew). If so, the sense is marked lexicalized=False. If all senses are lexicalized=False, or there are no other members, the synset is marked lexicalized=False.

Resolves #45

goodmami added 3 commits March 8, 2025 12:54
If a synset has a member GAP! or PSEUDOGAP!, that sense is removed and all
remaining senses are checked with heuristics to see if they are compositional
collocations (the presence of a space or apostrophe for Italian or a space for
Hebrew). If so, the sense is marked `lexicalized=False`. If all senses are
`lexicalized=False`, or there are no other members, the synset is marked
`lexicalized=False`.

Resolves #45
@goodmami goodmami merged commit 7026a93 into main Mar 10, 2025
@goodmami goodmami deleted the gh-45-lexical-gaps branch March 11, 2025 17:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

GAP! and PSEUDOGAP! entries

1 participant