Papers › Improving Interpretability of Deep Sequential Knowledge Tracing Models with...

Improving Interpretability of Deep Sequential Knowledge Tracing Models with Question-centric Cognitive Representations

14 Feb 2023arXiv:2302.06885archive 2025-07-28

Jiahao Chen, Zitao Liu, Shuyan Huang, Qiongqiong Liu, Weiqi Luo

Knowledge tracing (KT) is a crucial technique to predict students' future performance by observing their historical learning processes. Due to the powerful representation ability of deep neural networks, remarkable progress has been made by using deep learning techniques to solve the KT problem. The majority of existing approaches rely on the homogeneous question assumption that questions have equivalent contributions if they share the same set of knowledge components. Unfortunately, this assumption is inaccurate in real-world educational scenarios. Furthermore, it is very challenging to interpret the prediction results from the existing deep learning based KT models. Therefore, in this paper, we present QIKT, a question-centric interpretable KT model to address the above challenges. The proposed QIKT approach explicitly models students' knowledge state variations at a fine-grained level with question-sensitive cognitive representations that are jointly learned from a question-centric knowledge acquisition module and a question-centric problem solving module. Meanwhile, the QIKT utilizes an item response theory based prediction layer to generate interpretable prediction results. The proposed QIKT model is evaluated on three public real-world educational datasets. The results demonstrate that our approach is superior on the KT prediction task, and it outperforms a wide range of deep learning based KT models in terms of prediction accuracy with better model interpretability. To encourage reproducible results, we have provided all the datasets and code at https://pykt.org/.

PaperPDFCodeCode Syntology ranMethod as code

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 11 code samples harvested from 2 repositories linked to this paper: 8 ran (of which 5 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 2 where Syntology's instrument failed) · 3 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: community (archive-listed): 11 samples from 2 repositories, 8 ran (6 with no instrument failure; 2 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-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

ZhijieXiong/pyedmine pytorchSyntology: 3 samples, 2 ran (1 instrument-failed) · 1 unverified report
pykt-team/pykt-toolkit pytorchSyntology: 8 samples, 6 ran (1 instrument-failed) · 2 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

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

1ran · our draft was wrong
1ran; the contract check could not run
6ran
3unverified

Licence: 0 of the 11 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 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”. For 2 samples that ran, the graph records a signature this page does not show: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “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.

ZhijieXiong/pyedmine community (archive-listed) 3 samples, 2 ran (1 instrument-failed) · 1 unverified
MLP in 375 papers edmine/model/sequential_kt_model/QIKT.py ran fingerprinted MIT (permissive) · 7e570661ec2055e1 · report fixture: returned MLP · level recorded 2026-09-22
sigmoid_inverse edmine/model/sequential_kt_model/QIKT.py ran · our draft was wrong fingerprinted MIT (permissive) · 6bfa1fe3138c452f · report fixture: signature x:Tensor/2/float, epsilon:float/0/float · returned Tensor · level recorded 2026-09-22
QIKT edmine/model/sequential_kt_model/QIKT.py unverified MIT (permissive) · 9ad3588ca804907c · report
pykt-team/pykt-toolkit community (archive-listed) 8 samples, 6 ran (1 instrument-failed) · 2 unverified
MLP in 375 papers pykt/models/qikt.py ran MIT (permissive) · 391fc1018439e361 · report fixture: returned MLP · level recorded 2026-09-22
QIKT pykt/models/qikt.py ran MIT (permissive) · 30289d7d9c2392f4 · report fixture: returned QIKT · level recorded 2026-09-22
QueBaseModel pykt/models/qikt.py ran MIT (permissive) · 438cbf17f4ebb444 · report fixture: returned QueBaseModel · level recorded 2026-09-22
QueEmb pykt/models/qikt.py ran MIT (permissive) · e0192bd887c533f8 · report fixture: returned QueEmb · level recorded 2026-09-22
get_now_time pykt/models/qikt.py ran MIT (permissive) · 84856773d55a9836 · report fixture: returned str · level recorded 2026-09-22
get_outputs in 7 papers pykt/models/qikt.py ran; the contract check could not run (RAISES) MIT (permissive) · d64e5058e11fc74e · report fixture: signature self:callable/0/?, emb_qc_shift:Tensor/2/float, h:Tensor/2/float, data:dict/0/?, add_name:str/0/str, model_type:str/0/str · returned dict · level recorded 2026-09-22
QIKTNet pykt/models/qikt.py unverified MIT (permissive) · 29283795644f73af · report
debug_print pykt/models/qikt.py unverified MIT (permissive) · d5437c252c405c85 · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it. Siblings are assemblies lifted from this paper in the same batch for the same method: alternative readings kept side by side; none replaces or supersedes another.

2 assemblies on this paper: 2 harvested, 0 generated, listed in 1 groups (siblings lifted in one batch form one group).

2 sibling assemblies for QIKT (harvested), lifted in the same batch on 2026-09-09: alternative readings kept side by side; none replaces or supersedes another.

harvested Assembly for QIKT (graph method: QIKT). 8 bricks; individually on a fixture: 6 ran (of which 4 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 1 where Syntology's instrument failed) · 2 unverified. The assembly has not been run end-to-end.

one of 2 siblings

  1. QIKT entry · level 1 · ran · 30289d7d9c2392f4
  2. QIKTNet model · level 0 · unverified · 29283795644f73af
  3. QueBaseModel helper · level 1 · ran · 438cbf17f4ebb444
  4. debug_print helper · level 0 · unverified · d5437c252c405c85
  5. MLP helper · level 1 · ran · 391fc1018439e361
  6. QueEmb helper · level 1 · ran · e0192bd887c533f8
  7. get_outputs helper · level 1 · ran; the contract check could not run (RAISES) · d64e5058e11fc74e
  8. get_now_time helper · level 1 · ran · 84856773d55a9836

harvested Assembly for QIKT (graph method: QIKT). 8 bricks; individually on a fixture: 5 ran (of which 2 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 3 where Syntology's instrument failed) · 3 unverified. The assembly has not been run end-to-end.

one of 2 siblings

  1. QIKT entry · level 0 · unverified · 9ad3588ca804907c
  2. DLSequentialKTModel model · level 0 · unverified · 843a8076c769659a
  3. EmbedLayer helper · level 1 · ran · d15a23de22202ec8
  4. MLP model · level 1 · ran · 7e570661ec2055e1
  5. binary_cross_entropy loss · level 1 · ran; the contract check could not run · cba543ff01d32d68
  6. register_model helper · level 1 · ran · our draft was wrong · 7a822c04227645b1
  7. sigmoid_inverse helper · level 1 · ran · our draft was wrong · 6bfa1fe3138c452f
  8. KnowledgeTracingModel helper · level 0 · unverified · 583cf54d277de682

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2302.06885") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Deep LearningKnowledge TracingPrediction

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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