Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Clear methodology for masculine and feminine forms of words #973

Merged
merged 4 commits into from
Sep 26, 2023

Conversation

jmccrae
Copy link
Member

@jmccrae jmccrae commented Sep 20, 2023

This pull request fixes #883

I decided not to introduce an explicit relationship for masculine/feminine as there was not a clear way to proceed with this. This is due to there being several cases:

  1. A masculine term and a feminine term with a clear gender-neutral term ('policeman'/'policewoman'/'policeperson')
  2. A feminine term and a gender-neutral term ('actress'/'actor')
  3. Some terms where a gender-neutral synset does not exist or would be artificial (e.g. 'viscountess')

Instead, this change aims to ensure that no synset contains both a masculine and a feminine form, and wherever the forms are specifically gendered the synset is a hyponym of man 10306910-n or woman 10807146-n

@jmccrae jmccrae merged commit 8cc7c87 into main Sep 26, 2023
2 checks passed
@jmccrae jmccrae deleted the issue-883-v2 branch September 26, 2023 09:52
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.

New relation type for masculine/feminine form
1 participant