I don't know if eliminating ambiguity is even possible, much less a key feature of the language. There's even prominent ambiguity on this page:
> Lojban means different things to different people
> Lojban means different things to different people
Time flies like an arrow, fruit flies like a banana.
Of course, it's still possible to use Lojban to express statements that have an ambiguous or unclear meaning.
nTime vFlies avLike an nArrow, nFruit vFlies avLike a nBanana
Words in Hungarian have specific endings that change their "grammatical type" (I forget the grammatical term for that... part of speech?)
Some examples:
1. "-ás/-és": Transforms a verb into a noun that denotes an action or a profession. For example, the verb "tanul" (to study) becomes "tanulás" (study or studying).
2. "-ó/-ő": Converts a verb into a noun that refers to a person who does the action. For example, "tanít" (to teach) becomes "tanító" (teacher).
3. "-hat/-het": Added to a verb to form a new verb indicating possibility or permission. For example, "olvas" (reads) turns into "olvas-hat" (may/can read).
4. "-tlan/-tlen": When attached to a noun, it creates an adjective expressing the lack of something. For example, "szín" (color) becomes "színtelen" (colorless).
5. "-i": Added to a noun to create an adjective indicating origin or belonging. For example, "Amerika" (America) becomes "amerikai" (American).
6. "-ol": Attached to nouns to form verbs. This is often used with foreign words in Hungarian, like "ghosting-ol", "bullying-ol", "coworking-ol".
Additionally, in Hungarian these suffixes can be combined, so if you want to use the English noun "ghosting" as a noun in Hungarian, you still actually have to add the suffixes, so you would say "ghosting-ol-ás".
> The original Hungarian notation was invented by Charles Simonyi, a programmer who worked at Xerox PARC circa 1972–1981, and who later became Chief Architect at Microsoft. The name of the notation is a reference to Simonyi's nation of origin, and also, according to Andy Hertzfeld, because it made programs "look like they were written in some inscrutable foreign language". Hungarian people's names are "reversed" compared to most other European names; the family name precedes the given name. For example, the anglicized name "Charles Simonyi" in Hungarian was originally "Simonyi Károly". In the same way, the type name precedes the "given name" in Hungarian notation. The similar Smalltalk "type last" naming style (e.g. aPoint and lastPoint) was common at Xerox PARC during Simonyi's tenure there.
> Simonyi's paper on the notation referred to prefixes used to indicate the "type" of information being stored. His proposal was largely concerned with decorating identifier names based upon the semantic information of what they store (in other words, the variable's purpose). Simonyi's notation came to be called Apps Hungarian, since the convention was used in the applications division of Microsoft. Systems Hungarian developed later in the Microsoft Windows development team. Apps Hungarian is not entirely distinct from what became known as Systems Hungarian, as some of Simonyi's suggested prefixes contain little or no semantic information (see below for examples).
---
Simonyi's native language may have had some impact on how he wrote code, but it was not "human language -> write code like Hungarian -> Hungarian notation".
https://www.technologyreview.com/2007/01/01/227178/anything-...
> The resulting code was dense and hard to read. Simonyi’s system came to be known as Hungarian notation, both in homage to its creator’s birthplace and because it made programs “look like they were written in some inscrutable foreign language,” according to programming pioneer Andy Hertzfeld. Hungarian is widely cursed by its detractors. Canadian Java expert Roedy Green has jokingly called it “the tactical nuclear weapon of source code obfuscation techniques.” Mozilla programmer Alec Flett wrote this parody:
prepBut nI vrbLike adjHungarian! qWhat’s artThe adjBig nProblem?One of the books is the language guide to Ithkuil ( https://en.wikipedia.org/wiki/Ithkuil /// https://www.amazon.com/Grammar-Ithkuil-Language-John-Quijada... //// https://youtu.be/x_x_PQ85_0k )
This might fit some of your goals.
> nFruit nFlies vLike a nBanana
Actually, I am not sure that having different meanings of the same word in different contexts is really the problematic part causing ambiguity in conversations.
For example, sarcasm is a much more difficult problem. The words are the same, the meaning of the sentences is the same but the author's intent, the meaning behind those sentences is opposite if they are being sarcastic or not.
Lojban does not eliminate the ambiguity of the meaning of the words, but the ambiguity of its syntactical structure.
To me, the ambiguity of language, and the impracticality to change the meaning of words are the fundamental issues preventing humans to enhance the innate cognitive abilities, and the root cause of most human conflicts around communication.
Any profession and culture has its own jargon, this enables them to express the particular quality of their reality with much more accuracy than common language.
So, instead of trying to build a shared language, what we can do is to create a personal Language for each of us. Not for the purpose of communication, but for the purpose of improving our reasoning and internal model of the world, so we can describe and make sense of our particular reality with much more accuracy.
I've been dedicated to building "Interplanetary mind-map", a tool that supports making your language by making your meaning more explicit. [0]
At the same time, I've been using a prototype of it, to build my personal Language. You can browse into each word and see my particular understanding of it. [1]
[0] - https://github.com/interplanetarymindmap/docs
[1] - https://xavivives.com/#?expr=[%22i12D3KooWBSEYV1cK821KKdfVTH...
Specifically when not defining the ambigous concept „meaning“ and without sketching the assumed mechanism by which they are learned and turned into language.