Work with us

Tell us a bit about how you'd like to work with tri-bible.ai.

Semantic Analysis

Semantic Analysis

Several Uzbek terms in this Language Package carry a different semantic range than their English source word, and a number are shared directly with Islamic or Sufi religious vocabulary, which affects how consistently they can be used across contexts.

Terms shared with Islamic/Sufi vocabulary but semantically narrower in this curriculum

  • Iymon (faith): in everyday Uzbek Islamic usage, iymon denotes assent to the standard pillars of belief. This curriculum uses Iymon more narrowly: personal trust in Iso Masih. The object of faith must always be stated, since Iymon alone defaults to the broader Islamic sense for most readers.
  • Vositachilik (intercession): a generic word for mediation that must be actively distinguished from the much more devotionally loaded shafoat (Sufi shrine intercession); using the generic term is a deliberate choice to avoid importing shafoat’s specific theological content, not an oversight.
  • Shukronalik (thanksgiving): shares a root with shukur, a frequent devotional term in everyday Uzbek Islamic speech. This is a genuinely narrower usage than the broader Islamic devotional sense, but the overlap is a point of resonance rather than risk.

Terms narrower than their common Uzbek usage

  • Rabbiy (Lord): in general Uzbek usage rabbiy can appear as a title of respect, but this curriculum reserves it for the confession that Iso is Rabbiy — the unique, exclusive Lordship claim of Romans 10:9.
  • Muqaddas Ruh (Holy Spirit): broader Islamic commentary on “Ruh al-Qudus” often explains the phrase as referring to the archangel Jabroil; this curriculum narrows and redefines the term specifically as God the Holy Spirit, the third Person of the Trinity, and this redefinition must be made explicit, not assumed.

Implication

Where an Uzbek term’s common semantic range overlaps with, but does not match, its Islamic or Sufi theological usage, the glossary’s notes field (see translation_memory.json) exists specifically to flag the mismatch for translators, so a term is never applied on the assumption that a reader’s existing associations will automatically narrow correctly.