Twenty-five YouTube titles taken verbatim out of my video catalogue — three scripts in one line, half-decoded HTML entities, a title written in binary, a town called Leer — translated to English as strict JSON, each one echoed back beside its translation. The job I paid a GPU to do badly, handed to the expensive models.
6 videos featuring this round
Rounds stay open: later videos added their new models to this one.
You are the translation step in a pipeline that catalogues YouTube videos by the city they were filmed in. The titles below come out of the catalogue exactly as they were stored, including whatever decoration, encoding damage and spam the uploader left in. Your output is written straight to a database. Nothing downstream reads prose.
Below are 25 titles. Translate all of them into English.
Rules
Twenty-five in, twenty-five out, in the order given. Echo each id back exactly as written.
Echo the original title into orig, character for character. Copy it, do not retype it: every emoji, every stray backslash, every doubled space, every broken entity like " stays exactly as it arrived. This field is how a human reads your translation next to its source, so a "tidied" original is worse than useless — it hides what you were actually given.
Translate, do not transliterate. "Вечерний Рудногорск" is "Evening Rudnogorsk", not "Vecherniy Rudnogorsk". Proper nouns stay proper nouns; anything carrying meaning gets carried across.
A title already in English is copied verbatim. Do not improve it, re-case it, or tidy its punctuation.
Emoji stay, in the same position relative to the words. Same for hashtags: translate the words inside a hashtag only when it is a real phrase, and if that was a judgement call, say so in note.
Do not invent content. Where part of a title is damaged, masked, decorative, or not language at all, leave it alone and explain in note.
is for exceptions. Most rows should carry . A note on every row tells me nothing.
Answers
Sorted by cost. Open a row to load its answer.
note
""
Output
Raw JSON, nothing else — no markdown fence, no preamble, no commentary afterwards. Exactly this shape:
Keep the keys in that order, so a reader's eye lands on the original and the translation side by side.
lang — BCP-47 code for the dominant language of the original ("ja", "pt", "th"). Use "en" if it was already English, "und" if there is no language in it.
The batch
Each entry is an id line, then the title verbatim on the next line.
22:47
14:09
17:37
21:54
51:00
27:51