<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Learned in Translation: Contextualized Word Vectors · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1708.00107/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1708.00107/feed.xml" rel="self" type="application/rss+xml" /><item><title>Learned in Translation: Contextualized Word Vectors — mentioned by jph00</title><link>https://news.ycombinator.com/item?id=15524303</link><guid isPermaLink="false">urn:hackerpapers:mention:1708.00107:15524303</guid><pubDate>Sat, 21 Oct 2017 23:59:40 GMT</pubDate><description>&lt;p&gt;Word embeddings (or subword embeddings) are used for nearly all recent NLP algorithms, both shallow (e.g. FastText) and deep (e.g. Google Neural Translation). Unless you&amp;#x27;re using a basic bag-of-words approach, you need to translate your words into some vector format, so you probably want some kind of embeddings. In practice, all the state of the art approaches for translation, language modeling, classification (eg sentiment analysis), etc. all sit on top of embeddings. It&amp;#x27;s not word embeddings job to handle phrases - but nearly all modern phrase embedding algorithms sit on top of word…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1708.00107/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item></channel></rss>
