๐Ÿ“š Task Documentation

SemEval-2026 Shared Task
Attitude Polarization Detection in Multilingual News Commentary (POLAR)

Overview

This documentation provides all the details needed to understand, implement, and participate in the POLAR shared task. It includes dataset format, annotation scheme, task variants, evaluation metrics, and guidelines for submission.

๐Ÿงช Task Definition

Participants must develop models to detect and interpret attitude polarization in user comments from news discussions across multiple languages and topics. Given a news comment and context, the system should predict:

๐Ÿงฉ Subtasks

๐Ÿ—ƒ๏ธ Dataset

๐Ÿท๏ธ Annotation Guidelines

Polarized comments show strong alignment, antagonism, or emotional extremes toward social groups, ideologies, or policies. Cues include slurs, framing, emphasis, exaggeration, selective blame, etc. Native annotators provided culturally grounded judgments for each language.

A full annotation guideline document (PDF) will be made available on the Resources page.

๐Ÿงฎ Evaluation

๐Ÿ’พ Baseline Models

Baseline code and training scripts will be published on our GitHub repository.

๐Ÿš€ Submission Format

Prediction file: JSONL format
Required fields: id, label, and optionally cue_spans
Each team may submit up to 3 runs per subtask.

Submissions accepted via CodaLab during evaluation phase

๐Ÿ“… Timeline

Phase Date
31 March 2025 Call for Participation Opens / Task Proposals Due
8 August 2025 Trial Data Released
1 September 2025 Training Data Released
1 December 2025 Test Data Released (internal deadline; not for public release)
10 January 2026 System Submission Deadline / Evaluation Start
31 January 2026 Evaluation Results Released / Evaluation End
February 2026 System Paper Submission Deadline
March 2026 Notification of Acceptance
April 2026 Camera-Ready Papers Due
Summer 2026 SemEval-2026 Workshop at [Conference Location TBD]

๐Ÿ“Ž Resources

๐Ÿ“ฌ Contact

For any questions, reach out to us at:
๐Ÿ“ง polarization-semeval-2026-organisers@googlegroups.com
Or open an issue on GitHub Discussions