Which approach to interface translation should be chosen during localization (3 options)?

Question

Internationalization and localization

I decided to localize my service and ran into the following problem: the same words in English are translated into Russian differently depending on the context. That is, for example:
date -> date
date -> date (context - change the date)
How best to prepare the translation of words and phrases with this in mind?
Option 1 (ugly):

{	
  "date": "дата",
  "place": "место",
  "name": "название",
  "add": "добавить",
  "change": "изменить",
  "date_2": "дату"
}

these are date_2, date_3 - very inconvenient to maintain and reuse
Option 2 (expanding rapidly):

{
  "date": "дата",
  "place": "место",
  "name": "название",
  "add date": "добавить дату",
  "add place": "добавить место",
  "add name": "добавить название",
  "change date": "изменить дату",
  "change place": "изменить место",
  "change name": "изменить название"	
}

it turns out a very redundant number of elements, even in this simplest example - one and a half times
Option 3 (beautiful, but the code will be in Cyrillic):

{
  "дата": "date",
  "место": "place",
  "название": "name",
  "добавить": "add",
  "изменить": "change",
  "дату": "date"
}

It would be technically correct to choose the second option, especially given the possibility of adding other languages ​​in the future. But I'm still leaning towards the third option.
Which approach is better to choose? I would be grateful for a reasoned answer.
Thank you.

Answer 1

2.
Since: the key can be shown in cases where there is no translation.

Answer 2

hm. kindly if - the interface (views) should be separated from the code
which, again, if kindly - must be redone honestly
, otherwise interfaces with "Send." because in the original there was a short "Send"
or even worse - "User settings." instead of User Settings