Browse State-of-the-Art › Unsupervised Opinion Summarization
Unsupervised Opinion Summarization
5 papers with code · 3 benchmarks · 3 datasets archive 2025-07-28
Benchmarks archive 2025-07-28
3 leaderboard tables shown for this task, 3 with rows (a “benchmark” on this site is a table with at least one row, as on /sota), ordered by row count. “Best model” is the first row in the archive's own order at snapshot; nothing is re-ranked here and metric direction is not recorded in the archive. PwC's Trend sparklines are not in the archive, so that column is omitted.
| Dataset | Best model (first row in archive order) | Paper | Code | Syntology | Compare |
|---|---|---|---|---|---|
| Amazon (4 rows) | BiMeanVAE - Coop | Convex Aggregation for Opinion Summarization | code | — | Compare |
| Yelp (4 rows) | BiMeanVAE - Coop | Convex Aggregation for Opinion Summarization | code | — | Compare |
| SPACE (Opinion Summarization) (1 row) | Hercules (abstractive) | Attributable and Scalable Opinion Summarization | code | — | Compare |
Syntology column: samples harvested from the paper's repositories and executed on synthesized fixtures; “ran” is not a correctness claim and does not order the table. Each line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the row's paper, the line starts with that repository's state (“official” is the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from. A dash means no Syntology record for that paper, not a recorded non-run. Each “ran” line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.
Libraries
Not in the archive: the export carries no per-task library table, so there is nothing to show at snapshot 2025-07-28.
Datasets archive 2025-07-28
3 datasets whose archive record lists this task, ordered by the archive's paper count.
Subtasks archive 2025-07-28
No subtask under this task in the archive's task tree.
Parent tasks archive 2025-07-28
Papers archive 2025-07-28
archive papers tagged: 9 · with a code link: 5 · where Syntology ran a sample: 0 (0 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology
Show: all tagged papersonly where code ran: none of the 9 tagged papers has a Syntology run on record
Page 1 of 1: papers 1 to 9 of 9, in archive order: by repositories listed in the archive (most first), then newest first, not by stars (the archive holds no stars, so PwC's “Social” and “Latest” sorts cannot be reproduced). Papers that list no repository come after every paper that lists one.
Papers without a page here are shown as plain text. A Syntology line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the figure “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code); hover it for the repositories the samples that ran came from.
-
6 Nov 2019 3 repositories listedAt test time, when generating summaries, we force the novelty to be minimal, and produce a text reflecting consensus opinions.
-
19 May 2023 1 repository listedWe propose a method for unsupervised opinion summarization that encodes sentences from customer reviews into a hierarchical discrete latent space, then identifies common opinions based on the frequency of their…
-
3 Apr 2021 1 repository listedWe found that text autoencoders tend to generate overly generic summaries from simply averaged latent vectors due to an unexpected L₂-norm shrinkage in the aggregated latent vectors, which we refer to as summary vector…
-
14 Dec 2020 1 repository listedThe recent success of deep learning techniques for abstractive summarization is predicated on the availability of large-scale datasets.
-
21 Apr 2020 1 repository listedWe create a synthetic dataset from a corpus of user reviews by sampling a review, pretending it is a summary, and generating noisy versions thereof which we treat as pseudo-review input.
-
Automatically Evaluating Opinion Prevalence in Opinion Summarization26 Jul 2023 0 repositories listedWhen faced with a large number of product reviews, it is not clear that a human can remember all of them and weight opinions representatively to write a good reference summary.
-
Simple Yet Effective Synthetic Dataset Construction for Unsupervised Opinion Summarization21 Mar 2023 0 repositories listedOpinion summarization provides an important solution for summarizing opinions expressed among a large number of reviews.
-
Unsupervised Opinion Summarization Using Approximate Geodesics15 Sep 2022 0 repositories listedOpinion summarization is the task of creating summaries capturing popular opinions from user reviews.
-
OrderSum: Reading Order-Aware Unsupervised Opinion Summarization16 Nov 2021 0 repositories listedOpinion summarization aims to create a concise summary reflecting subjective information conveyed by multiple user reviews about the same product.
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