Papers › Graph-Based Reasoning over Heterogeneous External Knowledge for Commonsense Question Answering
Graph-Based Reasoning over Heterogeneous External Knowledge for Commonsense Question Answering
Shangwen Lv, Daya Guo, Jingjing Xu, Duyu Tang, Nan Duan, Ming Gong, Linjun Shou, Daxin Jiang, Guihong Cao, Songlin Hu
Commonsense question answering aims to answer questions which require background knowledge that is not explicitly expressed in the question. The key challenge is how to obtain evidence from external knowledge and make predictions based on the evidence. Recent works either learn to generate evidence from human-annotated evidence which is expensive to collect, or extract evidence from either structured or unstructured knowledge bases which fails to take advantages of both sources. In this work, we propose to automatically extract evidence from heterogeneous knowledge sources, and answer questions based on the extracted evidence. Specifically, we extract evidence from both structured knowledge base (i.e. ConceptNet) and Wikipedia plain texts. We construct graphs for both sources to obtain the relational structures of evidence. Based on these graphs, we propose a graph-based approach consisting of a graph-based contextual word representation learning module and a graph-based inference module. The first module utilizes graph structural information to re-define the distance between words for learning better contextual word representations. The second module adopts graph convolutional network to encode neighbor information into the representations of nodes, and aggregates evidence with graph attention mechanism for predicting the final answer. Experimental results on CommonsenseQA dataset illustrate that our graph-based approach over both knowledge sources brings improvement over strong baselines. Our approach achieves the state-of-the-art accuracy (75.3%) on the CommonsenseQA leaderboard.
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):
get_harvested_code_for_paper(arxiv_id="1909.05311")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="1909.05311", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="1909.05311")
Code
Syntology 17 code samples harvested from 1 repository linked to this paper: 12 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 2 honoured, 0 violated, 5 with no contract checked; 5 where Syntology's instrument failed) · 5 unverified. Where Syntology's instrument failed: 5 where our contract draft was wrong; failures of Syntology's instrument, not of the code.
By repository: official repository: 17 samples from 1 repository, 12 ran (7 with no instrument failure; 5 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-22 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 3 of the 12 samples that ran have no recorded date.
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
17 samples harvested: 12 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 2 honoured, 0 violated, 5 with no contract checked; 5 where Syntology's instrument failed) · 5 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.
Licence: 2 of the 17 samples are pointer only, meaning Syntology does not serve that copy's text. For 2 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 DecstionBack/AAAI_2020_CommonsenseQA. “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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.
census: 14 implementations from 37 papers, 2 distinct outputs on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32 pytorch_transformers/modeling_bert.py ran · our draft was wrong fingerprinted Apache-2.0 (permissive) ·
0f786c407fb1ee4c · report
fixture: signature x:Tensor/2/float · returned Tensor · level recorded, date not recorded census: 10 implementations from 13 papers, 4 distinct outputs across 4 buckets, one shared input per bucket this sample: bucket 1 of 4, arg 1: rank 2, kind float, dtype float32 pytorch_transformers/modeling_utils.py ran · honoured contract fingerprinted Apache-2.0 (permissive) here; the stored copy is pointer only ·
f44985272d18127a · report
fixture: signature x:Tensor/2/float · returned Tensor · level recorded, date not recorded 35ef111fc00c21b4 · report
fixture: signature model:callable/0/?, config:Config/0/? · returned dict · level recorded 2026-09-22 c92ba449e48ecffe · report
fixture: signature model:callable/0/?, config:Config/0/?, tf_weights:dict/0/? · returned dict · level recorded 2026-09-25 census: 43 implementations from 74 papers, 6 distinct outputs on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32 pytorch_transformers/modeling_gpt2.py ran · our draft was wrong fingerprinted Apache-2.0 (permissive) ·
8d23fbe2b99b840b · report
fixture: signature x:Tensor/2/float · returned Tensor · level recorded, date not recorded census: 43 implementations from 74 papers, 6 distinct outputs on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32 pytorch_transformers/modeling_bert.py ran · honoured contract fingerprinted Apache-2.0 (permissive) here; the stored copy is pointer only ·
fdc64f4c72036ae4 · report
fixture: signature x:Tensor/2/float · returned Tensor · level recorded 2026-09-22 census: 43 implementations from 74 papers, 6 distinct outputs on one shared input pytorch_transformers/modeling_xlnet.py ran fingerprinted Apache-2.0 (permissive) ·
b05b2bb38c0e4e72 · report
fixture: signature x:Tensor/2/float · returned Tensor · level recorded 2026-09-25 census: 43 implementations from 74 papers, 6 distinct outputs on one shared input pytorch_transformers/modeling_xlm.py ran fingerprinted Apache-2.0 (permissive) ·
b3c2618f6b7fb60c · report
fixture: signature x:Tensor/2/float · returned Tensor · level recorded 2026-09-25 f5d8d44f65a08b76 · report
fixture: signature slen:int/0/int, lengths:Tensor/1/int, causal:bool/0/bool, padding_mask:NoneType/0/? · returned tuple · level recorded 2026-09-25 7183a17dd79327a8 · report
fixture: signature layer:callable/0/?, index:Tensor/1/int, dim:int/0/int · returned Conv1D · level recorded 2026-09-25 d30d6c3098df2c42 · report
fixture: signature layer:callable/0/?, index:Tensor/1/int, dim:int/0/int · returned Linear · level recorded 2026-09-22 93228a3eb5c4d179 · report
fixture: signature embedding:callable/0/?, bias:Tensor/1/float, labels:Tensor/2/int, inputs:Tensor/3/float, sampler:LogUniformSampler/0/? · returned Tensor · level recorded 2026-09-22 03a94dbb436249a3 · report
07bb0220eb5b609f · report
42ee168c3ae12e60 · report
23d246e59ef9447b · report
4a94662ff3b5c5cf · report
Tasks
Results from the paper archive 2025-07-28
| Task | Dataset | Model | Metric | Value | Rank at snapshot | Leaderboard | Report |
|---|---|---|---|---|---|---|---|
| Common Sense Reasoning | CommonsenseQA | XLNet+GraphReason | Accuracy | 75.3 | #14 of 38 | 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