LongSocialBench: Do Long-Context LLMs Understand Online Discussion Threads?
Organizations: University of Illinois Urbana-Champaign · Semantic Code Lab
Abstract
Long-context LLMs can now ingest entire online discussion threads, but understanding their social discourse requires more than reading a long document: models must track parent-reply relations, turning points, scoped subtrees, cross-branch contrasts, and participant trajectories. To test this structure-aware social reasoning, we introduce LongSocialBench, a benchmark of 1,462 verified human-authored multiple-choice items drawn from 94 complete Hacker News, Stack Exchange, and Reddit r/ChangeMyView episodes, with a median length of approximately 73K tokens. Each item pairs a complete serialized discussion and reply structure with a four-option question, requiring models to recover structured social evidence. Released items are verified for answerability, option uniqueness, and evidence grounding. Across 18 models and 29 evaluation settings, current long-context workflows remain far below human performance. The best individual result comes from Claude-Opus-4.7, which reaches 63.0% when prompted to eliminate incorrect options before answering, compared with 72.4% for independent human readers. Averaged across all 18 models, the full-context Baseline scores 43.9%. Supplying the gold evidence scope raises this to 55.0%, showing that substantial errors remain even after the relevant thread region is identified. LongSocialBench shows that the missing capability is not context access or prompting alone, but social understanding over structured reply trees.
Figures & tables
| Area | Long | Thread | Social | Verif. |
| Long-context eval./agg. | ✓ | ✗ | ✗ | ✓ |
| Long-memory dialogue | ✓ | ✗ | ✓ | |
| Social commonsense/ToM | ✗ | ✗ | ✓ | ✓ |
| Argument / stance | ✓ | |||
| Discussion summarization | ✗ | |||
| Ours | ✓ | ✓ | ✓ | ✓ |
| Capability surface | Evidence focus |
|---|---|
| C1: Local social meaning | A comment’s social role or meaning in its local context. |
| C2: Reply-pair interaction | The relation between a reply and the parent comment it addresses. |
| C3: Collective structure | How positions or roles are distributed across a discussion region. |
| C4: Temporal dynamics | How an exchange changes over time, including shifts and turning points. |
| C5: Participant profile | A participant’s stance or interaction pattern across multiple comments. |
| C6: Cross-subdiscussion variation | How social patterns differ or remain consistent across branches or sub-discussions. |
| Baseline (Full-context) | CoT (with vs Baseline) | |||||||||||||
| Model | C1 | C2 | C3 | C4 | C5 | C6 | Avg | C1 | C2 | C3 | C4 | C5 | C6 | Avg |
| (Closed-source frontier) | ||||||||||||||
| Claude-Opus-4.7 | 74.5 | 65.2 | 49.1 | 67.0 | 54.1 | 50.0 | 60.0 | 79.4 | 71.9 | 53.1 | 70.8 | 65.6 | 59.3 | 66.7 |
| Gemini-2.5-Pro | 65.5 | 58.4 | 52.1 | 49.7 | 45.9 | 36.4 | 51.3 | 71.5 | 69.7 | 55.9 | 56.8 | 56.9 | 56.8 | 61.2 |
| GPT-5 | 61.8 | 68.5 | 43.7 | 58.9 | 63.8 | 53.4 | 58.3 | 67.9 | 80.9 | 44.3 | 49.7 | 63.3 | 58.5 | 60.8 |
| Claude-Sonnet-4.5 | 73.3 | 59.6 | 46.6 | 49.7 | 50.5 | 46.6 | 54.4 | 71.5 | 67.4 | 46.1 | 53.0 | 56.0 | 48.3 | 57.1 |
| Model tier | Full | Gold-Scope | |
|---|---|---|---|
| Closed frontier (6) | |||
| Strong open (4) | |||
| Mid open (4) | |||
| Small (4) | |||
| All 18 |
Appendix figures & tables26 assets
Supplementary material from the paper’s appendix.
Appendix
| Primary topic family | Total | HN | SE | |
|---|---|---|---|---|
| Computing / AI / internet | 25 | 20 | 0 | 5 |
| Economy / labor / business | 21 | 10 | 10 | 1 |
| Science / engineering / health | 17 | 3 | 5 | 9 |
| Public policy / law / governance | 11 | 6 | 4 | 1 |
| Culture / media / social life | 7 | 3 | 4 | 0 |
| Education / academia | 6 | 0 | 4 | 2 |
| Source | # eps | Tokens med. | Tokens max | Tokens total | Mean max-depth | Mean nodes | Mean root replies |
|---|---|---|---|---|---|---|---|
| Hacker News | 43 | 73,397 | 118,981 | 3.29M | 12.9 | 815.7 | 109.9 |
| Stack Exchange | 21 | 75,982 | 85,184 | 1.59M | 2.0 | 601.0 | 385.2 |
| Reddit r/CMV | 30 | 56,322 | 79,597 | 1.75M | 8.9 | 485.5 | 258.8 |
| Overall | 94 | 73K | 118,981 | 6.63M | 9.2 | 662.4 | 218.9 |
| Capability surface | Decision tested | Abridged example item |
|---|---|---|
| C1: Local social meaning | Decide what one comment is doing in context. | A target comment replies to a parent claim. Decide its local role : support, pushback, reframing, or clarification. |
| C2: Reply-pair interaction | Compare a reply with the comment it answers. | A parent uses one basis of comparison; the reply switches basis. Decide the parent reply relation : refute, qualify, redirect, or concede. |
| C3: Collective structure | Identify the positions organizing a scoped discussion region. | In a scoped subtree, choose the position structure that best organizes the replies: framing, consequences, responsibility, or evidence. |
| C4: Temporal dynamics | Locate where an ordered exchange changes direction. | In a long reply chain, identify the first turning point where one argumentative framing gives way to another. |
| C5: Participant profile | Track one participant across comments. | Across one author’s comments, infer the participant trajectory : stable stance, narrowed claim, concession, escalation, or strategy shift. |
| C6: Cross-subdiscussion variation | Compare behavior across separate branches. | Across two branches, decide the cross-branch change : whether a role, stance, or strategy stays stable or shifts. |
| Criterion | Requirement | Failure action |
|---|---|---|
| Answerability | The gold option is recoverable from the supplied episode alone, without external facts or author intent. | Rewrite or remove. |
| Option uniqueness | Exactly one option is supported under the stated scope and author-written criterion. | Revise options or remove. |
| Scope clarity | The stem specifies the relevant unit, such as a comment, direct-reply set, subtree, chain, participant trajectory, or cross-branch comparison. | Clarify stem and re-verify. |
| Evidence sufficiency | Evidence nodes support both the gold option and key premises such as branch boundary, counting unit, participant trajectory, or comparison set. | Add evidence, rewrite, or remove. |
| Observable social criterion | Interpretive questions are grounded in observable thread behavior rather than preference, speculation, or unstated norms. | Rewrite criterion or remove. |
| Option balance | Distractors are plausible wrong readings with comparable specificity, not fillers or wording artifacts. | Rewrite options and re-verify. |
| Control | Shortcut reduced | Authoring restriction |
|---|---|---|
| Minimal locators | The stem reveals the relevant node, chain, or subtree. | Use only the locator needed to define the scope; avoid exact quotes, usernames, redundant structural hints, or answer-implying descriptors. |
| Distributed evidence | A single salient comment solves a thread-level item. | Require evidence from the intended scope whenever the question asks for aggregation, comparison, trajectory, or cross-branch reasoning. |
| Controlled options | Option wording makes the answer obvious. | Use parallel option forms and close numeric or relational alternatives when appropriate; avoid answer-specific descriptive phrasing. |
| No hint vocabulary | Keyword search or hint words reveal the answer. | State the criterion without listing answer-bearing instances or repeating distinctive phrases from the gold evidence. |
| Diagnostic distractors | Distractors are implausible or too easy. | Tie distractors to plausible wrong scopes, wrong criteria, lexical matches, boundary errors, or aggregation mistakes. |
| Open-web contamination | The item is recoverable from open-web memory rather than the supplied episode. | Check distinctive stem/option phrases and named events; rewrite or exclude items whose answers can be recovered from open-web summaries or third-party transcripts. |
| Domain | Pass | Corrected | Residual |
|---|---|---|---|
| Hacker News | 44 / 46 | 2 / 46 | 0 / 46 |
| Reddit r/CMV | 32 / 32 | 0 / 32 | 0 / 32 |
| Stack Exchange | 22 / 22 | 0 / 22 | 0 / 22 |
| All | 98 / 100 | 2 / 100 | 0 / 100 |
| Model | Source | CW |
| Closed-source frontier systems | ||
| Claude-Opus-4.7 | Anthropic | 200K |
| GPT-5 | OpenAI | 400K |
| Claude-Sonnet-4.5 | Anthropic | 200K |
| Claude-4 | Anthropic | 200K |
| Gemini-2.5-Pro | 1M | |
| Setting group | Variants | Input construction and prompt |
| Deployable workflows | ||
| Full-context prompting | Full | The model receives the complete serialized discussion, reply-structure information, question stem, and four options; the prompt asks it to locate relevant evidence, compare options, and output one answer letter. |
| Reasoning prompts | CoT, CoT-Ev, CoT-Tp, CoT-El, Reflect | Same input as Full; the prompt adds one reasoning strategy before the final answer: free-form reasoning, evidence enumeration, temporal tracking, option elimination, or self-reflection. |
| Sparse retrieval | BM25- , BM25- | Comments are ranked by BM25 using the question stem as query; the top- comments are passed in original thread order and answered with the shared answer format. |
| Dense retrieval | E5- , E5- | Comments and question stems are embedded with E5; the top- comments by cosine similarity are passed in original thread order and answered with the shared answer format. |
| RAG with anchor notes | BM25/E5 anchors | Retrieved comments are supplemented with brief model-generated anchor notes that identify what each retrieved region contributes before final answering. |
| Model | Full | CoT | LLM-r | Best † | C-mac |
|---|---|---|---|---|---|
| (Closed-source frontier) | |||||
| Claude-Opus-4.7 | 56.0 | 61.8 | 55.3 | 63.0 | 60.0 |
| Gemini-2.5-Pro | 51.5 | 58.8 | 50.4 | 59.3 | 51.3 |
| GPT-5 | 52.9 | 53.8 | 50.3 | 56.4 | 58.3 |
| Claude-Sonnet-4.5 | 51.4 | 52.8 | 50.8 | 53.4 | 54.4 |
| Claude-4 | 52.0 | 52.5 | 50.5 | 53.5 | 57.0 |
| Family | Cells | Mean | 95% CI | Full |
| Chain-of-thought | 90 | 44.7 | [43.0, 46.5] | |
| Full-context | 18 | 43.9 | [41.3, 46.9] | — |
| RAG | 72 | 42.7 | [42.1, 43.2] | |
| RAG | 72 | 42.3 | [41.8, 42.8] | |
| LLM-as-retriever | 18 | 42.1 | [39.1, 45.4] | |
| Structure-aware retrieval | 54 | 41.1 | [39.6, 42.6] |
| Reader | Accuracy | # correct / 150 |
|---|---|---|
| R1 | 74.7 | 112 |
| R2 | 73.3 | 110 |
| R3 | 72.7 | 109 |
| R4 | 71.3 | 107 |
| R5 | 70.0 | 105 |
| Mean | 72.4 | 108.6 |
| Cohort | Mean | CI |
|---|---|---|
| Top single cell | ||
| Claude-Opus- | ||
| Closed-frontier mean ( ) | — | |
| Strong-open mean ( ) | — | |
| -model fleet mean | — | |
| Human readers ( ) |
| Model | CoT | CoT-Evid | CoT-Temp | CoT-Elim | Reflect | Mean |
|---|---|---|---|---|---|---|
| GLM-5 | +11.8 | +2.3 | +9.6 | +5.3 | +8.8 | +7.6 |
| Gemini-2.5-Pro | +7.3 | +4.4 | +7.8 | +7.0 | +5.5 | +6.4 |
| Claude-Opus-4.7 | +5.8 | +4.4 | +6.4 | +7.0 | +6.2 | +6.0 |
| Claude-Sonnet-4.6 | +7.3 | +3.8 | +6.9 | +6.1 | +5.3 | +5.9 |
| Llama-4-Mav-17B | +2.5 | -0.3 | +4.1 | +1.0 | +1.6 | +1.8 |
| GPT-5 | +0.9 | +0.3 | +1.2 | +2.6 | +3.4 | +1.7 |
| Retriever | Budget | Mean evidence recall |
|---|---|---|
| BM | 0.201 | |
| E | 0.203 | |
| BM | 0.308 | |
| E | 0.310 |
| Probe | Shortcut tested | Observed | Interpretation |
|---|---|---|---|
| Option-only | option prior | 31.5% | option text alone is insufficient |
| Question-only | stem leakage | 38.0% | question wording alone is insufficient |
| Title/root-only | topic familiarity | 35.4% | topic-level information is insufficient without replies |
| Shuffled thread | bag-of-comments inference | 40.4% | performance remains limited when local thread order is perturbed |
| Open-answer subset | multiple-choice artifact | pp; | absolute accuracy drops, but the model ranking is preserved |
| Tier | HN | SE | ||
|---|---|---|---|---|
| Closed frontier (6) | 53.0 | 49.1 | 51.1 | |
| Strong open (4) | 42.4 | 44.1 | 44.5 | |
| Mid open (4) | 41.3 | 39.3 | 39.8 | |
| Small (4) | 38.8 | 35.4 | 35.3 | |
| All 18 | 44.9 | 42.8 | 43.6 |
| Condition | Accuracy |
|---|---|
| CoT baseline | |
| Gold scope | |
| Gold per-comment labels | |
| Gold scope + gold labels | |
| Structured enumerate-label-aggregate pipeline |
| Error type | Share (%) |
|---|---|
| Criterion use | |
| Thread structure | |
| Counting rule | |
| Surface cue |
| Stage | Contributor task | Quality control |
|---|---|---|
| Authoring | Read the complete discussion, choose a clear scope, and write the question stem, four plausible options, gold option, plain-language criterion, and evidence nodes. | The item must require reasoning over the specified scope rather than topic familiarity or one salient comment. Distractors reflect plausible wrong readings, such as wrong scope, nearby count, boundary error, or near-synonym social label. |
| Artifact control | Remove answer-bearing wording from stems and options, including exact quotes, usernames, redundant structural hints, and distinctive phrases. | These controls reduce locator leakage, option-paraphrase matching, keyword shortcuts, and open-web contamination. Capability and item-form tags are retained only as metadata. |
| Independent verification | A different contributor re-answers the item from the same model-facing input used in evaluation: serialized thread, reply structure, question stem, and four answer options. | The verifier does not see the author’s gold option, criterion notes, evidence-node list, or rationale. Agreement checks answer stability and scope stability. |
| Adjudication | Phase-2 mismatches and author-flagged borderline cases receive a third-pass review. | The item is confirmed, clarified, rewritten and re-verified, or removed. A released item must have independent agreement or a stable adjudicated answer. |