adding query_verbs.sparql for kurmanji

[Khushalsarode]

Contributor checklist

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

Description

• The query has been executed & tested on wikidata editor
• Developed a SPARQL query to retrieve all Kurmanji (Q36163) verbs and their grammatical forms from Wikidata.
• Extracts lexeme IDs, verb forms, and various grammatical features including infinitive, gerund, accusative, and ergative.
• optional clauses to include additional forms such as adverbial, absolute construction, and participle

Issue reference

• Expand Kurmanji data queries #229

@andrewtavis

[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)

[andrewtavis]

Can we remove the extra spacing, @Khushalsarode? And also this ORDER BY is not necessary here as we don't need the results in a given order. This will end up just slowing the query down a bit :)

[Khushalsarode]

sure!

[Khushalsarode]

done as per requested! 👍

[andrewtavis]

Thanks for this, @Khushalsarode :) Ultimately I simplified the data down as there there don't appear to be any forms on the verbs, so this is one we'll need to do later. Nice touch on filtering the language to ku though 😊

[Khushalsarode]

shall I create separate query file for each in list?
@andrewtavis

[andrewtavis]

In the list in the issue, @Khushalsarode? Yes, please :)

[Khushalsarode]

In the list in the issue, @Khushalsarode? Yes, please :)

also I tried query for emoji's but no data has been prompted, Queried the kurmanji language against the emoji entity.
so should such queries be pushed or not, in case if data may be available in future?

[andrewtavis]

Ah, that's not how emojis work. We're not getting them from Wikidata, but rather from unicode. Check the emoji directories for other languages to see how it's done :) I'm not sure if Unicode has Kurmanji-emoji relationships though 🤔

[Khushalsarode]

Ah, that's not how emojis work. We're not getting them from Wikidata, but rather from unicode. Check the emoji directories for other languages to see how it's done :) I'm not sure if Unicode has Kurmanji-emoji relationships though 🤔

oh, I see my mistake. I checked the emoji directories for other languages. also read on internet that this unicode need to be only localize for different languages that doesn't change the unicode. nice!