Papers › Describing a Knowledge Base

Describing a Knowledge Base

6 Sep 2018WS 2018 11arXiv:1809.01797archive 2025-07-28

Qingyun Wang, Xiaoman Pan, Lifu Huang, Boliang Zhang, Zhiying Jiang, Heng Ji, Kevin Knight

We aim to automatically generate natural language descriptions about an input structured knowledge base (KB). We build our generation framework based on a pointer network which can copy facts from the input KB, and add two attention mechanisms: (i) slot-aware attention to capture the association between a slot type and its corresponding slot value; and (ii) a new table position self-attention to capture the inter-dependencies among related slots. For evaluation, besides standard metrics including BLEU, METEOR, and ROUGE, we propose a KB reconstruction based metric by extracting a KB from the generation output and comparing it with the input KB. We also create a new data set which includes 106,216 pairs of structured KBs and their corresponding natural language descriptions for two distinct entity types. Experiments show that our approach significantly outperforms state-of-the-art methods. The reconstructed KB achieves 68.8% - 72.6% F-score.

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

EagleW/Describing_a_Knowledge_Base officialmentioned in papermentioned on GitHubpytorchMITSyntology: 8 samples, 8 ran (5 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: 8 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 5 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 last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

5ran · our draft was wrong
3ran

Licence: 3 of the 8 samples are pointer only, meaning Syntology does not serve that copy's text. For 3 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 EagleW/Describing_a_Knowledge_Base. “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.

EagleW/Describing_a_Knowledge_Base official repository 8 samples, 8 ran (5 instrument-failed) · 0 unverified
cook_refs in 36 papers pycocoevalcap/cider/cider_scorer.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · 4c1b107103b7c856 · report fixture: signature refs:list/1/str, n:int/0/int · returned list · level recorded 2026-09-22
cook_refs in 36 papers pycocoevalcap/bleu/bleu_scorer.py ran · our draft was wrong MIT (permissive) · 7586e1d32f7325f7 · report fixture: signature refs:list/1/str, eff:str/0/str, n:int/0/int · returned tuple · level recorded 2026-09-25
cook_test in 35 papers pycocoevalcap/cider/cider_scorer.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only · 3573c4bc85f65dfd · report fixture: signature test:str/0/str, n:int/0/int · returned defaultdict · level recorded 2026-09-22
cook_test in 35 papers pycocoevalcap/bleu/bleu_scorer.py ran MIT (permissive) · 7ee8aa480d13ee01 · report fixture: signature test:str/0/str, ref_len_counts:tuple/1/int, eff:NoneType/0/?, n:int/0/int · returned dict · level recorded 2026-09-25
get_file_list_from_dir utils/split.py ran MIT (permissive) · edb9ea6d9e845789 · report fixture: signature datadir:str/0/str · returned list · level recorded 2026-09-25
precook in 38 papers pycocoevalcap/bleu/bleu_scorer.py ran · our draft was wrong fingerprinted MIT (permissive) · ec4448373d72d636 · report fixture: signature s:str/0/str, n:int/0/int, out:bool/0/bool · returned tuple · level recorded 2026-09-22
precook in 38 papers pycocoevalcap/cider/cider_scorer.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only · 9560e3e3e41bc1b2 · report fixture: signature s:str/0/str, n:int/0/int, out:bool/0/bool · returned defaultdict · level recorded 2026-09-22
split in 67 papers utils/split.py ran fingerprinted MIT (permissive) · 94b0f0677a61e291 · report fixture: signature file_list:list/1/str · returned tuple · level recorded 2026-09-25

Tasks

Data-to-Text GenerationKB-to-Language GenerationTable-to-Text GenerationText Generation

Datasets

Introduced by this paper, per the archive.

Wikipedia Person and Animal Dataset

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
KB-to-Language Generation Wikipedia Person and Animal Dataset KB-to-Language Generation Model BLEU 23.2 #1 of 1 Archive leaderboard report
KB-to-Language Generation Wikipedia Person and Animal Dataset KB-to-Language Generation Model METEOR 23.4 #1 of 1 Archive leaderboard report
KB-to-Language Generation Wikipedia Person and Animal Dataset KB-to-Language Generation Model ROUGE 42.0 #1 of 1 Archive leaderboard report
Table-to-Text Generation Wikipedia Person and Animal Dataset KB-to-Language Generation Model BLEU 23.2 #2 of 2 Archive leaderboard report
Table-to-Text Generation Wikipedia Person and Animal Dataset KB-to-Language Generation Model METEOR 42.0 #2 of 2 Archive leaderboard report
Table-to-Text Generation Wikipedia Person and Animal Dataset KB-to-Language Generation Model ROUGE 23.4 #2 of 2 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