Open Problems

Information Extraction & Entity Recognition

Semantic Typing and Grounding of Pronominal and Nominal Mentions Across Divergent Coreference Schemas

Effect to explainOpen
Possible candidate · 3/5 runs6 papers report this50% from 2025+

Generated automatically from the limitations stated in 6 papers (ACL, NAACL, EMNLP), listed under Evidence. It is not a paper, and it does not come from papers submitted to CSPaper.

The problem

Current entity recognition and extraction pipelines exhibit sharp performance drops when evaluated on schemas that include pronominal and nominal mentions, dropping to as low as 42% recall on datasets like ACE 2005. Because most taggers assume proper named entities, models fail to type clusters composed entirely of pronouns or misclassify ambiguous pronouns (such as mistaking collective 'we' as person rather than organization) in the absence of cross-sentence antecedent context. Consequently, roughly 10% or more of coreference mentions remain completely ungrounded or unassigned, preventing reliable document-level entity extraction.

Why it matters

Enables information extraction systems to resolve and semantically type document-level mentions regardless of whether they appear as proper names, nominal phrases, or pronouns.

Ways to approach it

Prior-work checks are free with an account. Results someone already ran are shown to everyone.

  1. 1

    Conduct a cross-dataset robustness evaluation across OntoNotes, ACE 2005, and OKE benchmarks to measure typing and grounding error distributions across mention types (proper, nominal, pronominal) and evaluate baseline drop-offs under divergent annotation conventions.

  2. 2

    Develop a joint mention-typing and coreference model that explicitly propagates entity-type posteriors along cross-sentential coreference chains to ungrounded pronouns and nominals, measuring MUC-F1, grounding accuracy, and pronominal type error rates.

  3. 3

    Design a schema-harmonization mapping method that aligns divergent mention boundaries (e.g., inclusion/exclusion of determiners and relative pronouns like 'which') without requiring manual re-annotation, measuring zero-shot cross-schema recall transfer.

Have a different approach?

Describe how you would tackle this problem and we'll look for papers that already do it. Free; your text stays private.

Free · 3 checks per day

Why it might fail

Long-context instruction-tuned large language models may dissolve this limitation via prompt-based extraction if they can resolve pronoun grounding and typing zero-shot without specialized architectures. Furthermore, persistent structural ambiguities in historical dataset annotation conventions may enforce a ceiling on cross-dataset schema transfer.

Evidence

Each paper's own statement of the limitation, verbatim.

Nearest existing work

Related open problems

Information Extraction & Entity Recognition

Barrier to removeOpen

Error-Aware Entity Linking Evaluation and Propagation-Bounded Pipelines for Downstream NLP Tasks

Virtually every system that touches entities — relation extraction, KBQA, semantic parsing, coreference, retrieval-augmented generation — treats entity linking as a solved preprocessing step and evaluates against gold links, so the systems' true field performance is unknown and unlinkable to their stated failure modes. When linking is wrong, downstream modules cannot detect, recover from, or bound the damage; reported failure analyses put linking errors at 15–35% of end-to-end errors. Today nobody can quantify how much of a downstream system's headroom is actually upstream, because no benchmark couples controlled link corruption with propagation measurement.

Strong candidate · 4/5 runs19 papers report this25% from 2025+

Information Extraction & Entity Recognition

Barrier to removeOpen

Quantifying and Mitigating Upstream Parser Brittleness in Syntactic Information Extraction

Syntactic-semantic information extraction pipelines depend strictly on upstream dependency parsers and part-of-speech taggers, leaving downstream relation and entity extraction vulnerable to cascading errors. When applied to domain-specific jargon or subjected to minor parser version updates, upstream accuracy drops and alters the extracted syntactic structures. This leaves practitioners unable to guarantee extraction stability across domains or library releases without manual parser fine-tuning.

Strong candidate · 4/5 runs3 papers report this33% from 2025+
Generated automatically, not curated by hand. Automated prior-work checks catch about a third of existing work, so treat this problem as a lead to investigate.