Papers › Distributed Representations of Sentences and Documents

Distributed Representations of Sentences and Documents

16 May 2014arXiv:1405.4053archive 2025-07-28

Quoc V. Le, Tomas Mikolov

Many machine learning algorithms require the input to be represented as a fixed-length feature vector. When it comes to texts, one of the most common fixed-length features is bag-of-words. Despite their popularity, bag-of-words features have two major weaknesses: they lose the ordering of the words and they also ignore semantics of the words. For example, "powerful," "strong" and "Paris" are equally distant. In this paper, we propose Paragraph Vector, an unsupervised algorithm that learns fixed-length feature representations from variable-length pieces of texts, such as sentences, paragraphs, and documents. Our algorithm represents each document by a dense vector which is trained to predict words in the document. Its construction gives our algorithm the potential to overcome the weaknesses of bag-of-words models. Empirical results show that Paragraph Vectors outperform bag-of-words models as well as other techniques for text representations. Finally, we achieve new state-of-the-art results on several text classification and sentiment analysis tasks.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 4 code samples harvested from 2 repositories linked to this paper: 4 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: community (archive-listed): 4 samples from 2 repositories, 4 ran (4 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

No sample is linked to this paper from 3 of its repositories that Syntology harvested for other papers:

Levels written on 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

27 repositories listed; official and paper-mentioned ones first.

Antonildo43/Classifica-o-de-textos-com-doc2Vec mentioned on GitHubMITSyntology: not harvested report
DCYN/Ramdomized-Clinical-Trail-Classification mentioned on GitHubtfSyntology: not harvested report
Nalydy/doc2vec mentioned on GitHubSyntology: not harvested report
TheCyberian/androidMalwareDetectionWithNLP mentioned on GitHubApache-2.0Syntology: 3 samples, 3 ran (0 instrument-failed) · 0 unverified report
TheCyberian/windowsMalwareDetectionWithNLP mentioned on GitHubApache-2.0Syntology: 1 sample, 1 ran (0 instrument-failed) · 0 unverified report
YinpeiDai/NAUM mentioned on GitHubtfMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Skip-Thought Vectors (arXiv:1506.06726; that paper's own run record: 2 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method. report
bombdiggity/paper-bag mentioned on GitHubtfSyntology: not harvested report
dhyeon/ingredient-vectors mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Distributed Representations of Words and Phrases and their Compositionality (arXiv:1310.4546; that paper's own run record: 21 ran (of which 2 constructed an object rather than computing a result; 20 with no instrument failure: 0 honoured, 0 violated, 20 with no contract checked; 1 where Syntology's instrument failed) · 5 unverified); nothing checks that they implement this paper's method. report
eske/multivec mentioned on GitHubApache-2.0Syntology: not harvested report
fabiocorreacordeiro/Elsevier_abstracts-Classification mentioned on GitHubSyntology: not harvested report
g-k-l/dsi-arxiv-recommender mentioned on GitHubSyntology: not harvested report
hithisisdhara/doc2vec mentioned on GitHubpytorchMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Document Embedding with Paragraph Vectors (arXiv:1507.07998; that paper's own run record: 0 ran · 1 unverified); nothing checks that they implement this paper's method. report
ibrahimsharaf/doc2vec mentioned on GitHubMITSyntology: not harvested report
inejc/paragraph-vectors mentioned on GitHubpytorchMITSyntology: not harvested report
jimmy6727/Informd mentioned on GitHubtfSyntology: not harvested report
julian-risch/ICADL2018 mentioned on GitHubtfSyntology: not harvested report
kinimod23/NMT_Project mentioned on GitHubSyntology: not harvested report
kitnhl/partisan-tweets-classification mentioned on GitHubSyntology: not harvested report
kr900910/supreme_court_opinion mentioned on GitHubtfSyntology: not harvested report
kramamur/sentiment-analysis mentioned on GitHubSyntology: not harvested report
rvstraalen/doc2vec-workshop mentioned on GitHubSyntology: not harvested report
slme1109/Lyrics_Generator_Using_LSTM mentioned on GitHubtfSyntology: not harvested report
slme1109/lyrics-generator mentioned on GitHubtfSyntology: not harvested report
tsandefer/capstone_2 mentioned on GitHubtfSyntology: not harvested report
tsandefer/dsi_capstone_2 mentioned on GitHubtfSyntology: not harvested report
vanboefer/nn_doc2vec_exercise mentioned on GitHubLGPL-3.0Syntology: not harvested report
wiflore/IBM_Articles_Recomender mentioned on GitHubApache-2.0Syntology: not harvested report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

4 samples harvested: 4 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

4ran

Licence: 0 of the 4 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

TheCyberian/androidMalwareDetectionWithNLP community (archive-listed) 3 samples, 3 ran (0 instrument-failed) · 0 unverified
list_dir in 22 papers doc2vec_training_plus_binary_classification.py ran Apache-2.0 (permissive) · ffa4cd04f2875291 · report fixture: signature directory:str/0/str · returned list · level recorded 2026-09-26
logistic_predictor_from_sklearn doc2vec_training_plus_binary_classification.py ran Apache-2.0 (permissive) · e53b2b396184b0c0 · report fixture: signature train_targets:ndarray/1/int, train_regressors:ndarray/2/float · returned LogisticRegression · level recorded 2026-09-26
retrieve_vectors utilities/vectorize_csv.py ran Apache-2.0 (permissive) · 4aa99ad90bcb852d · report fixture: signature doc2vec_model:MockDoc2VecModel/0/?, corpus_size:int/0/int, vectors_size:int/0/int, vector_type:str/0/str · returned ndarray · level recorded 2026-09-26
TheCyberian/windowsMalwareDetectionWithNLP community (archive-listed) 1 sample, 1 ran (0 instrument-failed) · 0 unverified
extract_name_attribute_from_xml xml2strings.py ran Apache-2.0 (permissive) · 5c8561d39b5f3185 · report fixture: signature xml_string:str/0/str · returned list · level recorded 2026-09-26

Tasks

Question AnsweringSentiment AnalysisText Classification

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Question Answering QASent Paragraph vector (lexical overlap + dist output) MAP 0.6762 #4 of 7 Archive leaderboard report
Question Answering QASent Paragraph vector (lexical overlap + dist output) MRR 0.7514 #4 of 7 Archive leaderboard report
Question Answering QASent Paragraph vector MAP 0.5213 #7 of 7 Archive leaderboard report
Question Answering QASent Paragraph vector MRR 0.6023 #7 of 7 Archive leaderboard report
Question Answering WikiQA Paragraph vector (lexical overlap + dist output) MAP 0.5976 #24 of 25 Archive leaderboard report
Question Answering WikiQA Paragraph vector (lexical overlap + dist output) MRR 0.6058 #24 of 25 Archive leaderboard report
Question Answering WikiQA Paragraph vector MAP 0.5110 #25 of 25 Archive leaderboard report
Question Answering WikiQA Paragraph vector MRR 0.5160 #25 of 25 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections