Browse › Natural Language Processing › Natural Language Understanding › GLUE

Natural Language Understanding archive 2025-07-28

GLUE Benchmark (Natural Language Understanding)

2 rows 2 with code listed 1 metric Dataset page

Syntology Since the archive (Syntology): none placed; 11 newer papers judged to report on this board so far.

Natural Language Understanding is an important field of Natural Language Processing which contains various tasks such as text classification, natural language inference and story comprehension. Applications enabled by natural language understanding range from question answering to automated reasoning.

Source: Find a Reasonable Ending for Stories: Does Logic Relation Help the Story Cloze Test?

The archive carries no text for this table; the description above is the archive's text for the task Natural Language Understanding. archive 2025-07-28

Over time archive 2025-07-28

Not inferred: Average. Points are placed at the row's paper date, not an evaluation date; 2 of 2 rows carry one.

The chart needs JavaScript; the table below carries every value.

Results archive 2025-07-28

Archive rows end at the archive snapshot, 2025-07-28: no result published after that date is in this table. Rank is the archive's row order at that snapshot; not re-ranked here. Metric values are the archive's strings. Column headers sort the table in your browser; each row keeps its archive rank.

Paper Code Ran Syntology Report
1 MT-DNN-SMART 89.9 – Paper Code 2019 official: no sample here; runs from other or unrecorded repositories · 8 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 2 honoured, 1 violated, 2 with no contract checked; 3 where Syntology's instrument failed) · 0 unverified report
2 BERT-LARGE 82.1 – Paper Code 2018 official: no sample here; runs from other or unrecorded repositories · 300 ran (of which 75 constructed an object rather than computing a result; 234 with no instrument failure: 18 honoured, 5 violated, 211 with no contract checked; 66 where Syntology's instrument failed) · 359 unverified report

All 2 rows shown. 2 link to a paper page on this site; 0 are marked as using additional training data in the archive. No GitHub stars are tracked; "Code" is the first repository the archive lists for the row. The archive carries no row tags, review links or community-submitted rows for this table; none are shown. archive 2025-07-28

Syntology Ran 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”: of the code samples Syntology harvested from repositories linked to that row's paper (joined by arXiv id), N executed on a synthesized input and U are unverified (harvested, no recorded run). Of the N, C constructed an object rather than computing a result (a part of N, never taken away from it), K ran with no instrument failure (honoured or violated the contract Syntology drafted, or ran with no contract checked) and I are failures of Syntology's instrument, not of the code (a wrong contract draft, or a contract check that could not run). It counts code from repositories linked to that row's paper, not this result: the row's number was not reproduced and nothing here is a correctness claim. The other cell texts mean no graph line for the row: "linked, not harvested" (the archive links code, Syntology has not harvested it), "no code linked" (no code link in the archive), "not matched" (the row's paper URL matched no paper on this site). 2 rows have a graph line, from 2 distinct papers. Rows whose paper has a sample that ran: 2 (2 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument). Papers: 2 with a sample that ran: 2 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument. Whose code ran. When the archive marks a repository official for the row's paper, the cell starts with that repository's state (“official” is the archive's flag, not a verdict on who wrote the code): “official (archive's flag): N ran” counts the samples from it that ran, instrument failures included; “official: harvested, nothing ran”; when it has no sample for this paper and other samples ran, “community repositories only” if every one came from a repository the archive lists for the paper but neither marks official nor records as mentioned in it, or one Syntology harvested outside the archive's links, and “official: no sample here; runs from other or unrecorded repositories” if any came from a repository named in the paper or found in its text by Syntology, or has no repository recorded; “official: harvested for another paper” (no sample from it is linked to this paper) or “official: not harvested”. No state is printed when the archive marks none official. The cell's tooltip names the repositories the samples that ran came from. Of the 2 rows with a graph line, 2 have an archive-official repository: on 0 a sample from it ran (0 with a run with no instrument failure), on 0 the samples that ran came from community repositories only, and on 2 from other or unrecorded repositories. The filters above hide rows and never renumber them; the first two count, by default, only a run with no instrument failure, and offer any run, instrument failures included. Counting each paper once, of 667 samples: 308 ran (of which 75 constructed an object rather than computing a result; 239 with no instrument failure: 20 honoured, 6 violated, 213 with no contract checked; 69 where Syntology's instrument failed) · 359 unverified. Separately, 165 of those 667 are pointer-only (licence): the site points at that code rather than redistributing it, a licence property recorded for ran and unverified samples alike; each cell's tooltip carries the row's own pointer-only count. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. Per-sample status is on the paper page; each Ran cell links to that paper's sample list. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.

Since the archive Syntology

Of the 8,888 newer papers whose tables Syntology has read (8,886 checked in full and 2 with a leaderboard still awaiting a verdict), 33 had this board among the leaderboards the extractor considered for their tables (it keeps at most 10 boards per paper and 4 per dataset; the lists of 1,580 of the 8,888 were already full without this board, so if it was crowded out of them it is not counted), and 11 proposed a result; of those 11, 9 gave no cell that passed the extractor's own checks, 2 were rejected by the independent check, 0 await a verdict and 0 were placed. Syntology has checked 8,886 of the 18,637 papers on this site that are newer than the archive (for 3,717 of them no archive leaderboard matched the paper's tables, so there was nothing further to check); 733 were read and have nothing to place (arXiv has no HTML version of the paper, or that version has no tables), 41 could not be read (the extractor's reply could not be parsed), and results from the other 8,977 appear after they are checked.

Newer papers whose tables Claude Sonnet 4.5 judged to report on this benchmark (a model's judgement, not a result; newest first by arXiv id)

Paper arXiv date Ran Syntology Outcome
Fine-Tuning of Transformer models with Frames arXiv:2608.26430 26 Aug 2026 4 harvested: 4 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 3 where Syntology's instrument failed) · 0 unverified refused by a rule: the table's column header does not name the leaderboard's metric
Epiplexity Guided Data Selection and Generation for Out-of-Distribution Generalization arXiv:2608.11746 12 Aug 2026 16 harvested: 10 ran (of which 1 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 1 violated, 1 with no contract checked; 8 where Syntology's instrument failed) · 6 unverified refused by a rule: the value is not on the scale of the leaderboard column's archive values
Essential Subspace Merging for Multi-Task Learning arXiv:2606.19164 17 Jun 2026 10 harvested: 9 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 8 where Syntology's instrument failed) · 1 unverified refused by a rule: the table's column header does not name the leaderboard's metric
SSR-Merge: Subspace Signal Routing for Training-Free LoRA Merging in Diffusion Models arXiv:2606.10617 9 Jun 2026 held, no recorded run refused by a rule: the table's column header does not name the leaderboard's metric
Give it Space! Explicit Disentangling of Positional and Semantic Representations in Encoders arXiv:2605.30022 28 May 2026 12 harvested: 10 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 2 honoured, 0 violated, 4 with no contract checked; 4 where Syntology's instrument failed) · 2 unverified refused by a rule: the table's column header does not name the leaderboard's metric
TLoRA: Task-aware Low Rank Adaptation of Large Language Models arXiv:2604.18124 20 Apr 2026 6 harvested: 6 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 1 violated, 0 with no contract checked; 5 where Syntology's instrument failed) · 0 unverified rejected by the independent check
Polynomial Expansion Rank Adaptation: Enhancing Low-Rank Fine-Tuning with High-Order... arXiv:2604.11841 12 Apr 2026 18 harvested: 15 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 1 violated, 2 with no contract checked; 12 where Syntology's instrument failed) · 3 unverified refused by a rule: the table's column header does not name the leaderboard's metric
DAPA: Distribution Aware Piecewise Activation Functions for On-Device Transformer... arXiv:2603.19338 19 Mar 2026 1 harvested: 1 ran (of which 1 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified; the one sample that ran constructed an object rather than computing a result refused by a rule: several configurations of the method, and no metric direction to pick one
From O(mn) to O(r²): Two-Sided Low-Rank Communication for Adam in Distributed Training... arXiv:2602.08007 8 Feb 2026 3 harvested: 2 ran (of which 2 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; every one of the 2 samples that ran constructed an object rather than computing a result refused by a rule: the table's column header does not name the leaderboard's metric
Diving into Kronecker Adapters: Component Design Matters arXiv:2602.01267 1 Feb 2026 11 harvested: 11 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 2 honoured, 0 violated, 4 with no contract checked; 5 where Syntology's instrument failed) · 0 unverified rejected by the independent check
FOAM: Blocked State Folding for Memory-Efficient LLM Training arXiv:2512.07112 8 Dec 2025 6 harvested: 5 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 4 where Syntology's instrument failed) · 1 unverified refused by a rule: the table's column header does not name the leaderboard's metric

Syntology 11 newer papers judged to report on this board: the papers counted above as having proposed a result (0 placed); every one is listed here and in the JSON twin. The order is the arXiv identifier's, newest first, not a rank. The judgement is the model's, read from the paper's own tables; the outcome is what Syntology's checks did with it, and no value from a paper that was not placed is printed. “refused by a rule” names the extractor's rule; “no cell passed the extractor's checks” means the extractor's record holds no cell for this board, passed or refused. The 9 counted above as giving no cell that passed the extractor's own checks are the 9 marked “refused by a rule”. Drawn from 8,886 of 18,637 newer papers checked so far (733 more had nothing to place; 41 could not be read).

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