A model Sheba built
Sheba Yemen 1 understands Yemeni users in the Arabic they write, not the Arabic of textbooks.
Sheba built it to run inside its own products and deployments wherever they serve Yemeni users. Reading the culture behind the words is part of that job.
The dialect, and the culture it carries
Sheba Yemen 1 was built to take a request’s cultural context into account, not the words alone, because a word can mean one thing to a Yemeni user and another in a dictionary.
This page describes that understanding rather than acting it out, so it carries no dialect samples and no figures.
Where it runs
Nobody opens it as an app of its own. It works as part of a system people already use: Sheba's products and deployments, wherever those serve Yemeni users.
Status and access
No API, no weights, no price and no licence. There is no standalone access: Sheba Yemen 1 runs inside Sheba's systems.
What it shows about Sheba's model work
Sheba Yemen 1 is one of the models Sheba builds and fine-tunes for what its own products and deployments need. A use case in your organisation can start the same kind of work, and what it produces is a model built or fine-tuned for that case, never access to this one.
Explore Sheba's model workFAQ
It is not offered on its own, and that raises three questions
Your use case might need a model of its own. The way one market writes already did.
Whether your case needs a model of its own shows in the requests it receives and the language they arrive in, so start by describing those to us.
Discuss model work for your use case