Browse State-of-the-Art › Slot Filling

Slot Filling

140 papers with code · 14 benchmarks · 27 datasets archive 2025-07-28

Natural Language Processing

The goal of Slot Filling is to identify from a running dialog different slots, which correspond to different parameters of the user’s query. For instance, when a user queries for nearby restaurants, key slots for location and preferred food are required for a dialog system to retrieve the appropriate information. Thus, the main challenge in the slot-filling task is to extract the target entity.

Source: Real-time On-Demand Crowd-powered Entity Extraction

Image credit: Robust Retrieval Augmented Generation for Zero-shot Slot Filling

Description from the archive archive 2025-07-28.

Benchmarks archive 2025-07-28

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

Syntology 1 newer paper was judged to report on this task's benchmarks so far (Claude Sonnet 4.5, reading their tables: a model's judgement, not a result; 0 placed): MixSNIPS (1 judged, 0 placed), MixATIS (1 judged, 0 placed). Drawn from 8,886 of 18,637 newer papers checked so far (733 more had nothing to place; 41 could not be read).

DatasetBest model (first row in archive order)PaperCodeSyntologyCompare
KILT: Zero Shot RE (21 rows) single ngram — — — Compare
KILT: T-REx (20 rows) Re2G Re2G: Retrieve, Rerank, Generate code Syntology official (archive's flag): 7 ran · 7 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 1 where Syntology's instrument failed) · 1 unverified Compare
MixSNIPS (16 rows) BiSLU Joint Multiple Intent Detection and Slot Filling with Supervised... code — Compare
MixATIS (15 rows) MISCA MISCA: A Joint Model for Multiple Intent Detection and Slot... code — Compare
ATIS (14 rows) CTRAN CTRAN: CNN-Transformer-based Network for Natural Language Understanding code — Compare
SNIPS (10 rows) CTRAN CTRAN: CNN-Transformer-based Network for Natural Language Understanding code — Compare
SLURP (5 rows) TDT 0-6 Efficient Sequence Transduction by Jointly Predicting Tokens and Durations code Syntology community repositories only · 1 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; 0 where Syntology's instrument failed) · 1 unverified Compare
MASSIVE (3 rows) XLM-R Base MASSIVE: A 1M-Example Multilingual Natural Language Understanding... code Syntology official (archive's flag): 1 ran · 8 ran (of which 0 constructed an object rather than computing a result; 8 with no instrument failure: 0 honoured, 1 violated, 7 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified Compare
CAIS (1 row) CM-Net CM-Net: A Novel Collaborative Memory Network for Spoken Language... code — Compare
Dialogue State Tracking Challenge (1 row) MIDAS MIDAS: Multi-level Intent, Domain, And Slot Knowledge Distillation... code — Compare
MULTIWOZ 2.2 (1 row) MIDAS MIDAS: Multi-level Intent, Domain, And Slot Knowledge Distillation... code — Compare
Polyvore (1 row) Fashion GAE Context-Aware Visual Compatibility Prediction code — Compare
ProSLU (1 row) General SLU Model w/ Profile Text is no more Enough! A Benchmark for Profile-based Spoken... code — Compare
ATIS (vi) (1 row) JointBERT-CAE CAE: Mechanism to Diminish the Class Imbalanced in SLU Slot Filling Task 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

27 datasets whose archive record lists this task, ordered by the archive's paper count.

Subtasks archive 2025-07-28

2 subtasks in the archive's task tree.

Papers archive 2025-07-28

archive papers tagged: 458 · with a code link: 140 · where Syntology ran a sample: 18 (15 with a run with no instrument failure, 3 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (18 of 458 tagged: 15 with a run with no instrument failure, 3 where every run was a failure of Syntology's instrument)

Page 1 of 5: papers 1 to 100 of 458, 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 15 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