Papers › METGEN: A Module-Based Entailment Tree Generation Framework for Answer Explanation

METGEN: A Module-Based Entailment Tree Generation Framework for Answer Explanation

5 May 2022Findings (NAACL) 2022 7arXiv:2205.02593archive 2025-07-28

Ruixin Hong, Hongming Zhang, Xintong Yu, ChangShui Zhang

Knowing the reasoning chains from knowledge to the predicted answers can help construct an explainable question answering (QA) system. Advances on QA explanation propose to explain the answers with entailment trees composed of multiple entailment steps. While current work proposes to generate entailment trees with end-to-end generative models, the steps in the generated trees are not constrained and could be unreliable. In this paper, we propose METGEN, a Module-based Entailment Tree GENeration framework that has multiple modules and a reasoning controller. Given a question and several supporting knowledge, METGEN can iteratively generate the entailment tree by conducting single-step entailment with separate modules and selecting the reasoning flow with the controller. As each module is guided to perform a specific type of entailment reasoning, the steps generated by METGEN are more reliable and valid. Experiment results on the standard benchmark show that METGEN can outperform previous state-of-the-art models with only 9% of the parameters.

PaperPDFConference PDFCodeCode 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 15 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) · 8 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 2 samples from 1 repository, 0 ran (0 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 13 samples from 1 repository, 7 ran (7 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.

Raising-hrx/MetGen officialmentioned on GitHubpytorchSyntology: 2 samples, 0 ran · 2 unverified report
2023-MindSpore-1/ms-code-145 mentioned on GitHubmindsporeSyntology: not harvested report
tencent-ailab/metalogic mentioned on GitHubpytorchMITSyntology: 13 samples, 7 ran (0 instrument-failed) · 6 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

15 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) · 8 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
8unverified

Licence: 0 of the 15 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”. “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.

Raising-hrx/MetGen official repository 2 samples, 0 ran · 2 unverified
inference_alltype_batch code/reasoning.py unverified Apache-2.0 (permissive) · b8079af0c4132e0a · report
module_generate code/reasoning.py unverified Apache-2.0 (permissive) · 00efe99655a93027 · report
tencent-ailab/metalogic community (archive-listed) 13 samples, 7 ran (0 instrument-failed) · 6 unverified
add_prefix in 20 papers code/MultitaskGenerator.py ran MIT (permissive) · beba7770688234ee · report fixture: signature prefix:str/0/str, datas:list/1/dict · returned list · level recorded 2026-09-24
average_metric code/evaluate_metric.py ran MIT (permissive) · 5eec4de27f0a807e · report fixture: signature scores:list/1/dict · returned dict · level recorded 2026-09-24
compute_f1 in 40 papers code/evaluate_metric.py ran fingerprinted MIT (permissive) · 6724ecbf0decf84e · report fixture: signature matched:int/0/int, predicted:int/0/int, gold:int/0/int · returned tuple · level recorded 2026-09-24
div in 13 papers code/evaluate_metric.py ran fingerprinted MIT (permissive) · afa489d8ecd9a6b0 · report fixture: signature num:int/0/int, denom:int/0/int · returned float · level recorded 2026-09-24
remove_given_tokens code/tree_utils.py ran MIT (permissive) · 085a151d0f4302bb · report fixture: signature input_str:str/0/str, remove_list:list/1/str · returned str · level recorded 2026-09-24
results_three_components code/show_results.py ran MIT (permissive) · fa555ae62592ef54 · report fixture: signature path:str/0/str · returned dict · level recorded 2026-09-24
transform_by_dict code/tree_utils.py ran MIT (permissive) · 95f196e28e3cebb0 · report fixture: signature input_str:str/0/str, mapping_dict:dict/0/? · returned str · level recorded 2026-09-24
compute_ppl in 10 papers code/inference.py unverified MIT (permissive) · 2e5c0702c50628ea · report
eval_triples_by_operator code/show_results.py unverified MIT (permissive) · b9f140e483016d14 · report
load_model in 479 papers code/inference.py unverified MIT (permissive) · bb8883844e1d86f0 · report
model_inference code/inference.py unverified MIT (permissive) · cd4093a904b501e5 · report
preprocess_raw_data code/tree_utils.py unverified MIT (permissive) · 136e8658ff8e991a · report
train_one_step in 8 papers code/ModuleGenerator.py unverified MIT (permissive) · eadaf1fa3927a98e · report

Tasks

Question Answering

1 archive task tag without a task page not shown.

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