Papers › Bridging the KB-Text Gap: Leveraging Structured Knowledge-aware Pre-training for KBQA

Bridging the KB-Text Gap: Leveraging Structured Knowledge-aware Pre-training for KBQA

28 Aug 2023arXiv:2308.14436archive 2025-07-28

Guanting Dong, Rumei Li, Sirui Wang, Yupeng Zhang, Yunsen Xian, Weiran Xu

Knowledge Base Question Answering (KBQA) aims to answer natural language questions with factual information such as entities and relations in KBs. However, traditional Pre-trained Language Models (PLMs) are directly pre-trained on large-scale natural language corpus, which poses challenges for them in understanding and representing complex subgraphs in structured KBs. To bridge the gap between texts and structured KBs, we propose a Structured Knowledge-aware Pre-training method (SKP). In the pre-training stage, we introduce two novel structured knowledge-aware tasks, guiding the model to effectively learn the implicit relationship and better representations of complex subgraphs. In downstream KBQA task, we further design an efficient linearization strategy and an interval attention mechanism, which assist the model to better encode complex subgraphs and shield the interference of irrelevant subgraphs during reasoning respectively. Detailed experiments and analyses on WebQSP verify the effectiveness of SKP, especially the significant improvement in subgraph retrieval (+4.08% H@10).

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

By repository: official repository: 10 samples from 1 repository, 10 ran (10 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 on 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

dongguanting/skp-for-kbqa officialmentioned in papermentioned on GitHubpytorchSyntology: 10 samples, 10 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

10 samples harvested: 10 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 0 where Syntology's instrument failed) · 0 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.

10ran

Licence: 10 of the 10 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from dongguanting/skp-for-kbqa. “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.

dongguanting/skp-for-kbqa official repository 10 samples, 10 ran (0 instrument-failed) · 0 unverified
default_data_collator DPR_pretraining/data_collactor.py ran fingerprinted no licence file found · pointer only · 9377eb8058dfa617 · report fixture: signature features:list/1/dict, return_tensors:str/0/str · returned dict · level recorded 2026-09-24
get_answers in 5 papers DPR_inference/fid_preprocess.py ran no licence file found · pointer only · e671c895df132135 · report fixture: signature question:dict/0/? · returned set · level recorded 2026-09-24
get_entities in 12 papers DPR_inference/fid_preprocess.py ran no licence file found · pointer only · 24a0d889f41f7882 · report fixture: signature question:dict/0/? · returned set · level recorded 2026-09-24
get_fid DPR_inference/fid_preprocess.py ran fingerprinted no licence file found · pointer only · 76e71b6742137d91 · report fixture: signature s:str/0/str · returned str · level recorded 2026-09-24
list_to_str in 7 papers DPR_pretraining/main_bert.py ran no licence file found · pointer only · 0f18cce9ec62f6e6 · report fixture: signature list:list/1/str · returned str · level recorded 2026-09-24
mask_mask DPR-main/train_dense_encoder_mask.py ran no licence file found · pointer only · 5a6dd8868629358f · report fixture: signature context_ids:list/1/list, tensorizer:MockTensorizer/0/? · returned ndarray · level recorded 2026-09-24
ner_mask DPR_pretraining/main_bert.py ran fingerprinted no licence file found · pointer only · 39eb9ce1e34b3d1c · report fixture: signature text:list/1/str, label:list/1/str · returned tuple · level recorded 2026-09-24
ner_preprocess DPR_pretraining/main_bert.py ran no licence file found · pointer only · 87d6dbae98f9c70a · report fixture: signature file_path:str/0/str, file_path2:str/0/str · returned list · level recorded 2026-09-24
tf_default_data_collator DPR_pretraining/data_collactor.py ran no licence file found · pointer only · 899f3144b20efb88 · report fixture: signature features:list/1/dict · returned dict · level recorded 2026-09-24
torch_default_data_collator DPR_pretraining/data_collactor.py ran no licence file found · pointer only · 0e912aec22029af8 · report fixture: signature features:list/1/dict · returned dict · level recorded 2026-09-24

Tasks

Knowledge Base Question AnsweringQuestion AnsweringRetrieval

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Knowledge Base Question Answering WebQuestionsSP SKP Hits@1 79.6 #3 of 8 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.

Methods

BASE

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