Add SPARQL query for extracting Urdu adjectives (#242)

[Ekikereabasi-Nk]

Contributor checklist

• This pull request is on a separate branch and not the main branch

---

Description

This pull request introduces a new SPARQL query designed to retrieve Urdu adjectives and their grammatical forms from Wikidata. The query is inspired by the SPARQL code from the "Expand Scribe-Data Hindi verb queries" by KesharwaniArpita, and it aims to enhance our understanding and representation of Urdu lexicographical data.

Key features of the query:

1. Fetches the adjective's lemma (base form) from Wikidata.
2. Retrieves various grammatical forms associated with each adjective.
3. Filters results to include only forms where the language is set to "ur" (Urdu).
4. Displays the lexeme ID, lemma, and optional grammatical features for each result.

Context and significance:

• This query is part of a broader effort to document and analyze Hindustani (Q11051), also known as Hindi-Urdu, a language spoken widely in India and Pakistan.

• While this specific query focuses on Urdu adjectives, it complements existing work on Hindi verbs, reflecting the close relationship between Hindi and Urdu within the Hindustani language complex.

The SPARQL query has been validated using the Wikidata Query Service
-->

Related issue

• Related to Create Urdu adjectives extraction query #242

[github-actions]

Thank you for the pull request!

The Scribe team will do our best to address your contribution as soon as we can. The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

If you're not already a member of our public Matrix community, please consider joining! We'd suggest using Element as your Matrix client, and definitely join the General and Data rooms once you're in. Also consider joining our bi-weekly Saturday dev syncs. It'd be great to have you!

Maintainer checklist

• The commit messages for the remote branch should be checked to make sure the contributor's email is set up correctly so that they receive credit for their contribution

  • The contributor's name and icon in remote commits should be the same as what appears in the PR
  • If there's a mismatch, the contributor needs to make sure that the email they use for GitHub matches what they have for git config user.email in their local Scribe-Data repo

• The linting and formatting workflow within the PR checks do not indicate new errors in the files changed

• The CHANGELOG has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)

[KesharwaniArpita]

@Ekikereabasi-Nk You may want to check out the following QID for your grammatical feature:
Singulative Numeral: Q110786
Collective Numeral: Q146786
Oblique Case: Q1233197

[Ekikereabasi-Nk]

@KesharwaniArpita Thank you very much for the information. I will look at it

[Ekikereabasi-Nk]

Hi @andrewtavis the files have been restored to their original state as requested. All unnecessary file/folder have been removed, ensuring the pull request only includes the intended work.

[andrewtavis]

I did a couple of minor edits here, @Ekikereabasi-Nk, but looking at some of the data it seems like there are many forms that we could still include or also make more specific by adding more properties to each form. Do you want to expand the current query and then we'll be good to merge? 😊

[Ekikereabasi-Nk]

Hi @andrewtavis thanks for review and providing feedback. I appreciate your suggestion to expand the current query by including more forms and adding more properties to each form. I'm open to expanding the query as you've suggested

[andrewtavis]

Sounds great, @Ekikereabasi-Nk! Looking forward to the further commits! 😊

[Ekikereabasi-Nk]

Hi @andrewtavis I have worked on expanding, and updated the queries for urdu adjectives. Please take a look. Thank you

[andrewtavis]

As with the other ones, we need to combine the properties to get individual forms. Let's work towards doing this in future queries, @Ekikereabasi-Nk 😊 Thanks so much for the efforts here!