Papers › Global-Locally Self-Attentive Dialogue State Tracker

Global-Locally Self-Attentive Dialogue State Tracker

19 May 2018arXiv:1805.09655archive 2025-07-28

Victor Zhong, Caiming Xiong, Richard Socher

Dialogue state tracking, which estimates user goals and requests given the dialogue context, is an essential part of task-oriented dialogue systems. In this paper, we propose the Global-Locally Self-Attentive Dialogue State Tracker (GLAD), which learns representations of the user utterance and previous system actions with global-local modules. Our model uses global modules to share parameters between estimators for different types (called slots) of dialogue states, and uses local modules to learn slot-specific features. We show that this significantly improves tracking of rare states and achieves state-of-the-art performance on the WoZ and DSTC2 state tracking tasks. GLAD obtains 88.1% joint goal accuracy and 97.1% request accuracy on WoZ, outperforming prior work by 3.7% and 5.5%. On DSTC2, our model obtains 74.5% joint goal accuracy and 97.5% request accuracy, outperforming prior work by 1.1% and 1.0%.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 8 code samples harvested from 2 repositories linked to this paper: 7 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 5 samples from 1 repository, 4 ran (4 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 3 samples from 1 repository, 3 ran (3 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-25 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

salesforce/glad officialmentioned in papermentioned on GitHubpytorchBSD-3-ClauseSyntology: 5 samples, 4 ran (0 instrument-failed) · 1 unverified report
kolk/MODELING-ASR-AMBIGUITY-FOR-NEURAL-DIALOGUE-STATE-TRACKING-USING-WORD-CONFUSION-NETWORKS mentioned on GitHubpytorchBSD-3-ClauseSyntology: 3 samples, 3 ran (0 instrument-failed) · 0 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

8 samples harvested: 7 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

7ran
1unverified

Licence: 7 of the 8 samples are pointer only, meaning Syntology does not serve that copy's text. For 4 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

salesforce/glad official repository 5 samples, 4 ran (0 instrument-failed) · 1 unverified
attend models/glad.py ran BSD-3-Clause (permissive) · 250b450ed46b01f5 · report fixture: signature seq:Tensor/3/float, cond:Tensor/2/float, lens:list/1/int · returned tuple · level recorded 2026-09-25
missing_files preprocess_data.py ran fingerprinted BSD-3-Clause (permissive) here; the stored copy is pointer only · 84d277412226d70d · report fixture: signature d:str/0/str, files:list/1/str · returned bool · level recorded 2026-09-25
pad in 85 papers models/glad.py ran BSD-3-Clause (permissive) here; the stored copy is pointer only · a972bbc41289b9a2 · report fixture: signature seqs:list/1/list, emb:callable/0/?, device:str/0/str, pad:int/0/int · returned tuple · level recorded 2026-09-25
run_rnn models/glad.py ran BSD-3-Clause (permissive) here; the stored copy is pointer only · 13617250dc021474 · report fixture: signature rnn:callable/0/?, inputs:Tensor/3/float, lens:ndarray/1/int · returned Tensor · level recorded 2026-09-25
load_model in 479 papers utils.py unverified BSD-3-Clause (permissive) here; the stored copy is pointer only · a87c666aeb87d9c4 · report
kolk/MODELING-ASR-AMBIGUITY-FOR-NEURAL-DIALOGUE-STATE-TRACKING-USING-WORD-CONFUSION-NETWORKS community (archive-listed) 3 samples, 3 ran (0 instrument-failed) · 0 unverified
cnet_best_n_paths dataset_dstc_clean_asr.py ran BSD-3-Clause recorded; this copy not marked cleared · pointer only · b9c0143f90bd1d57 · report fixture: signature confusion_network:list/1/list, n:int/0/int, paths:list/1/empty · returned list · level recorded 2026-09-26
get_cnet_best_pass utils.py ran BSD-3-Clause recorded; this copy not marked cleared · pointer only · b5fec3b473d9f0d1 · report fixture: signature cnet:list/1/list, eos:str/0/str, null_:str/0/str, sos:str/0/str · returned list · level recorded 2026-09-26
load_model in 479 papers utils.py ran BSD-3-Clause recorded; this copy not marked cleared · pointer only · 556de295149cb83e · report fixture: signature model:str/0/str · returned MagicMock · level recorded 2026-09-26

Tasks

Dialogue State TrackingMulti-domain Dialogue State TrackingTask-Oriented Dialogue Systems

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Dialogue State Tracking Second dialogue state tracking challenge Zhong et al. Area - #3 of 7 Archive leaderboard report
Dialogue State Tracking Second dialogue state tracking challenge Zhong et al. Food - #3 of 7 Archive leaderboard report
Dialogue State Tracking Second dialogue state tracking challenge Zhong et al. Joint 74.5 #3 of 7 Archive leaderboard report
Dialogue State Tracking Second dialogue state tracking challenge Zhong et al. Price - #3 of 7 Archive leaderboard report
Dialogue State Tracking Second dialogue state tracking challenge Zhong et al. Request 97.5 #3 of 7 Archive leaderboard report
Dialogue State Tracking Wizard-of-Oz Zhong et al. Joint 88.1 #8 of 10 Archive leaderboard report
Dialogue State Tracking Wizard-of-Oz Zhong et al. Request 97.1 #8 of 10 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

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