# Rebuilding a Field's Open-Problem Catalog from the Literature: A Two-Layer Knowledge Graph, and Why Status Must Stay Proposed

DevFeed: [Rebuilding a Field's Open-Problem Catalog from the Literature: A Two-Layer Knowledge Graph, and Why Status Must Stay Proposed](<https://devfeed.tech/articles/rebuilding-a-field-s-open-problem-catalog-from-the-literature-a-two-layer-knowledge-graph-and-why-status-must-stay-proposed-108220.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.39641>)

Author: Madhulatha Mandarapu, Sandeep Kunkunuru

Published: 2026-10-30T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>), [arXiv: Databases](<https://devfeed.tech/sources/arxiv-databases.md>)

Topics: [graph-database](<https://devfeed.tech/topics/graph-database.md>), [Entity resolution](<https://devfeed.tech/topics/entity-resolution.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [abstract](<https://devfeed.tech/tags/abstract.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-research](<https://devfeed.tech/tags/ai-research.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [audit](<https://devfeed.tech/tags/audit.md>), [build](<https://devfeed.tech/tags/build.md>), [can](<https://devfeed.tech/tags/can.md>), [candidate](<https://devfeed.tech/tags/candidate.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-db](<https://devfeed.tech/tags/cs-db.md>), [cs-dl](<https://devfeed.tech/tags/cs-dl.md>), [field](<https://devfeed.tech/tags/field.md>), [graph](<https://devfeed.tech/tags/graph.md>), [knowledge](<https://devfeed.tech/tags/knowledge.md>), [knowledge-graph](<https://devfeed.tech/tags/knowledge-graph.md>), [layer](<https://devfeed.tech/tags/layer.md>), [literature](<https://devfeed.tech/tags/literature.md>), [open](<https://devfeed.tech/tags/open.md>), [status](<https://devfeed.tech/tags/status.md>), [two-layer](<https://devfeed.tech/tags/two-layer.md>)

## AI overview

The paper builds a queryable open-problem catalog by keeping a hand-curated problem layer intact and joining it to a bibliographic evidence layer that is rebuilt, using typed links with provenance. Its language model extracts paper details, grounds them to catalog entries, proposes per-paper status verdicts, and generates ideas; each task is limited to candidate sets so unsupported matches are rejected. On catalogs of 1,053 database problems and 1,000 AI problems, the graph retained nearly all prior catalog-only question coverage (47/47 and 34/35) and enabled queries about recent workers, untouched problems, methods, and related outside papers. Status judgments were unreliable: of 41 checked solve/refute verdicts, 9 were correct, 30 partly correct, and 2 wrong; none of 34 refutes disproved an open problem, and 1 of 7 solves closed the central question. The authors therefore require status changes to remain evidence-backed proposals for human review, and identify entity resolution, verification, source-quota freshness, and evaluation without ground truth as remaining challenges.

## Source excerpt

arXiv:2610.39641v1 Announce Type: cross Abstract: A research field records its open problems in surveys, keynotes and community reports. Those are prose, written every few years, and nobody can ask them who works on a problem now or whether it was settled last year. We argue the problems should be data, and we build the system that makes them so: a hand-curated problem layer carried in unchanged, under an evidence layer rebuilt from a bibliographic index, joined by typed, provenance-carrying links in one graph database and queryable from one language. A language model does four jobs -- per-paper extraction, catalog grounding, per-paper status verdict, and idea generation -- each constrained to a candidate set so out-of-set answers are refused rather than stored. We report a study on two curated catalogs, database research (1,053 problems) and AI research (1,000 problems), each with a prior catalog-only graph. The rebuilt graph answers every question the catalog-only graph answered -- 47 of 47 on databases, 34 of 35 on AI -- plus questions the catalog-only graph refused: recent workers, untouched problems, methods tried, and outside papers bearing on a problem (336 problems, 770 works on databases). The capability we most wanted does not survive its own audit. Of 41 solves and refutes verdicts hand-checked against the papers, 9 are correct, 30 partly correct and 2 wrong; no refutes verdict (0 of 34) disproves an open problem, and only 1 of 7 solves closes the central question. We report that failure in full and draw the design conclusion: a status change must be proposed with its evidence and never applied, making the human reviewer part of the architecture. We close with the data-engineering problems this raises: entity resolution across curated and harvested layers, verifying model status claims, freshness under source quotas, and evaluation without ground truth.