Docs
CommunityJev Benchmarks & Evaluations
MFRC
A social-jev dataset for MFRC: labelled rows pair query types, polarity, messages and targets across 312 train, 39 validation and 39 test examples, and the original config keeps 17,844 rows with subreddit and vote metadata.
- Format
- Docs
- Reading time
- 2 min
- Published by
- Community
- Author
- SocialJev
- Last verified
- Oct 2026
Highlights
- Labelled config: 312 train, 39 validation and 39 test rows with query_types, polarity, messages and integer targets.
- Original config: 17,844 rows of text with label definitions, vote proportions and spans.
- Original metadata adds subreddit, bucket, position and voting_annotator_count fields.
- Assignments list per-annotator records with position, annotator, annotation and confidence.
- Sized 10K–100K examples; parquet and text, with datasets, dask and polars tagged.
Watch out
Card reviewed 2026-10-17; the card is a dataset_info schema with no prose, no stated licence and no provenance notes, so label semantics are undocumented; counts come from the metadata block, and labelled and original are two views of the same material.
Questions about this entry
Short answers drawn from the linked project or page.
A social-jev dataset repo for MFRC: a labelled config of 312 train, 39 validation and 39 test typed-decision rows, plus an original config holding 17,844 rows of source text with annotation records.
Rows carry id, document_id, model, query_types, polarity, role/content messages, integer targets and a source_revision field; the split sizes are 312 train, 39 validation and 39 test.
17,844 text rows with label records carrying id, label, definition, aggregation, distribution values with counts and proportions, plus spans when present, and metadata with subreddit, bucket, position and annotator counts.
Yes: the assignments list records position, annotator, annotation text and a confidence value per annotator, alongside the aggregated label distribution for each row.
No licence is stated anywhere on the card; only the size, format and library tags are present, so verify the upstream MFRC terms before any reuse.
It mirrors the typed-decision shape — a text state, a set of query types and per-option targets — but the card gives no prose about how the targets were labelled or what the query types mean.
Treat the schema as the only documentation: there is no task description, provenance or baseline on the card, and the source_revision field hints at an upstream snapshot that is not further described.
From the Jev guides
Original write-ups on what this entry is for.
From the Jev AI model community
Posts from builders shipping with Jev right now.