Browse State-of-the-Art › Semantic Parsing

Semantic Parsing

414 papers with code · 20 benchmarks · 44 datasets archive 2025-07-28

Natural Language Processing

Semantic Parsing is the task of transducing natural language utterances into formal meaning representations. The target meaning representations can be defined according to a wide variety of formalisms. This include linguistically-motivated semantic representations that are designed to capture the meaning of any sentence such as λ-calculus or the abstract meaning representations. Alternatively, for more task-driven approaches to Semantic Parsing, it is common for meaning representations to represent executable programs such as SQL queries, robotic commands, smart phone instructions, and even general-purpose programming languages like Python and Java.

Source: Tranx: A Transition-based Neural Abstract Syntax Parser for Semantic Parsing and Code Generation

Description from the archive archive 2025-07-28.

Benchmarks archive 2025-07-28

20 leaderboard tables shown for this task, 20 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. 10 shown of 20 until expanded.

DatasetBest model (first row in archive order)PaperCodeSyntologyCompare
WikiTableQuestions (22 rows) ARTEMIS-DA ARTEMIS-DA: An Advanced Reasoning and Transformation Engine for... — — Compare
spider (10 rows) RESDSQL-3B + NatSQL RESDSQL: Decoupling Schema Linking and Skeleton Parsing for Text-to-SQL code Syntology official: harvested, nothing ran · 0 ran · 1 unverified Compare
CFQ (5 rows) Dynamic Least-to-Most Prompting Compositional Semantic Parsing with Large Language Models — — Compare
WebQuestionsSP (5 rows) ReaRev ReaRev: Adaptive Reasoning for Question Answering over Knowledge Graphs code — Compare
WikiSQL (5 rows) NL2SQL-BERT Content Enhanced BERT-based Text-to-SQL Generation code — Compare
ATIS (4 rows) PhraseTransformer PhraseTransformer: An Incorporation of Local Context Information... code — Compare
Geo (3 rows) coarse2fine Coarse-to-Fine Decoding for Neural Semantic Parsing code Syntology official (archive's flag): 4 ran · 4 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified Compare
PTG (czech, MRP 2020) (3 rows) PERIN + RobeCzech RobeCzech: Czech RoBERTa, a monolingual contextualized language... — — Compare
AMR (chinese, MRP 2020) (2 rows) PERIN ÚFAL at MRP 2020: Permutation-invariant Semantic Parsing in PERIN code — Compare
AMR (english, MRP 2020) (2 rows) PERIN ÚFAL at MRP 2020: Permutation-invariant Semantic Parsing in PERIN code — Compare
DRG (english, MRP 2020) (2 rows) PERIN ÚFAL at MRP 2020: Permutation-invariant Semantic Parsing in PERIN code — Compare
DRG (german, MRP 2020) (2 rows) PERIN ÚFAL at MRP 2020: Permutation-invariant Semantic Parsing in PERIN code — Compare
EDS (english, MRP 2020) (2 rows) PERIN ÚFAL at MRP 2020: Permutation-invariant Semantic Parsing in PERIN code — Compare
PTG (english, MRP 2020) (2 rows) PERIN ÚFAL at MRP 2020: Permutation-invariant Semantic Parsing in PERIN code — Compare
SQA (2 rows) TAPEX-Large TAPEX: Table Pre-training via Learning a Neural SQL Executor code — Compare
UCCA (english, MRP 2020) (2 rows) PERIN ÚFAL at MRP 2020: Permutation-invariant Semantic Parsing in PERIN code — Compare
UCCA (german, MRP 2020) (2 rows) PERIN ÚFAL at MRP 2020: Permutation-invariant Semantic Parsing in PERIN code — Compare
complexWebQuestions-V1.0 (1 row) HSP Complex Question Decomposition for Semantic Parsing code — Compare
GraphQuestions (1 row) ReasonBERTR ReasonBERT: Pre-trained to Reason with Distant Supervision code Syntology official (archive's flag): 9 ran · 9 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 1 honoured, 1 violated, 5 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified Compare
SParC (1 row) MeMCE Memory-Based Semantic Parsing 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

44 datasets whose archive record lists this task, ordered by the archive's paper count. 30 shown of 44 until expanded.

Subtasks archive 2025-07-28

7 subtasks in the archive's task tree.

Papers archive 2025-07-28

archive papers tagged: 1,202 · with a code link: 414 · where Syntology ran a sample: 96 (80 with a run with no instrument failure, 16 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (96 of 1,202 tagged: 80 with a run with no instrument failure, 16 where every run was a failure of Syntology's instrument)

Page 1 of 13: papers 1 to 100 of 1,202, 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. The first sentence of the abstract is shown for the first 30 papers; every abstract is on its paper's page.

Syntology lines on 39 of the papers shown; no Syntology record for the others (a paper without an arXiv id cannot be joined to the graph, and absence from the graph layer is not a recorded non-run). “Ran” means the sample executed on a synthesized fixture, not that the paper's result was reproduced; each 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.

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