Skip to content
OpenTrain AIFor AI Companies

HFEPX · Eval paper review

LastWords: Boring Problems Revisited

Huayang Li, Richard Sproat

Published

Oct 17, 2026

Citations

0

Trust level

Low

Usefulness score

0/100 (Low)

Extraction confidence

15% (Low)

Derived from extracted protocol signals and abstract evidence.

Rater population

Not reported

Signals refreshed

Oct 17, 2026

Should you rely on this paper?

This paper is adjacent to HFEPX scope and is best used for background context, not as a primary protocol reference.

Use this as background context only. Do not make protocol decisions from this page alone.

Best use

Background context only

Use if you need

Background context only.

What to verify

Read the full paper before copying any benchmark, metric, or protocol choices.

Main weakness

This paper looks adjacent to evaluation work, but not like a strong protocol reference.

Human feedback signal
Not explicit
Not explicit in abstract metadata
Evaluation signal
Weak or implicit
Validate from full paper
Usefulness for eval research
0/100
Adjacent candidate

Treat as adjacent context, not a core eval-method reference.

Abstract

In 2022, the second author published a Last Words piece in Computational Linguistics in which he pointed out that, despite the advances in AI up to that point, there were still some problems in natural language processing that on the one hand seemed trivial and perhaps boring, but on the other were hard to solve using purely neural methods. One such problem discussed in that context was text normalization, and a particular subproblem of that, namely number name reading. The piece came out just a few months before the first release of ChatGPT, and needless to say, a lot has happened since then. Indeed, as we document here, the problem (of number name reading) has practically been solved, at least by one of the latest frontier models. However, we believe that there are still open issues for such limited domain, constrained and limited resource problems, and that in some future machine learning approach, the massive resources of the latest frontier models would not be needed to solve them.

What we could verify

These are the protocol signals we could actually recover from the available paper metadata. Use them to decide whether this paper is worth deeper reading.

Human Feedback Types

missing

None explicit

No explicit feedback protocol extracted.

"In 2022, the second author published a Last Words piece in Computational Linguistics in which he pointed out that, despite the advances in AI up to that point, there were still some problems in natural language processing that on the one hand seemed trivial and perhaps boring, but on the other were hard to solve using purely neural methods."

Evaluation Modes

missing

None explicit

Validate eval design from full paper text.

"In 2022, the second author published a Last Words piece in Computational Linguistics in which he pointed out that, despite the advances in AI up to that point, there were still some problems in natural language processing that on the one hand seemed trivial and perhaps boring, but on the other were hard to solve using purely neural methods."

Quality Controls

missing

Not reported

No explicit QC controls found.

"In 2022, the second author published a Last Words piece in Computational Linguistics in which he pointed out that, despite the advances in AI up to that point, there were still some problems in natural language processing that on the one hand seemed trivial and perhaps boring, but on the other were hard to solve using purely neural methods."

Benchmarks / Datasets

missing

Not extracted

No benchmark anchors detected.

"In 2022, the second author published a Last Words piece in Computational Linguistics in which he pointed out that, despite the advances in AI up to that point, there were still some problems in natural language processing that on the one hand seemed trivial and perhaps boring, but on the other were hard to solve using purely neural methods."

Reported Metrics

missing

Not extracted

No metric anchors detected.

"In 2022, the second author published a Last Words piece in Computational Linguistics in which he pointed out that, despite the advances in AI up to that point, there were still some problems in natural language processing that on the one hand seemed trivial and perhaps boring, but on the other were hard to solve using purely neural methods."

Benchmarks and datasets

No benchmark or dataset names were extracted from the available abstract.

Reported metrics

No metric terms were extracted from the available abstract.

Human feedback details
Uses human feedback
No
Feedback types
None
Rater population
Not reported
Expertise required
General
Evaluation details
Evaluation modes
None
Agentic eval
None
Quality controls
Not reported
Evidence quality
Low
Use this page as
Background context only

Research brief

Metadata summary

In 2022, the second author published a Last Words piece in Computational Linguistics in which he pointed out that, despite the advances in AI up to that point, there were still some problems in natural language processing that on the one hand seemed trivial and perhaps boring, but on the other were hard to solve using purely neural methods.

Based on abstract + metadata only. Check the source paper before making high-confidence protocol decisions.

Key takeaways

  • In 2022, the second author published a Last Words piece in Computational Linguistics in which he pointed out that, despite the advances in AI up to that point, there were still some problems in natural language processing that on the one hand seemed trivial and perhaps boring, but on the other were hard to solve using purely neural methods.
  • One such problem discussed in that context was text normalization, and a particular subproblem of that, namely number name reading.
  • The piece came out just a few months before the first release of ChatGPT, and needless to say, a lot has happened since then.

Researcher actions

  • Compare this paper against nearby papers in the same arXiv category before using it for protocol decisions.
  • Check the full text for explicit evaluation design choices (raters, protocol, and metrics).
  • Use related-paper links to find stronger protocol-specific references.

Caveats

  • Generated from abstract + metadata only; no PDF parsing.
  • Signals below are heuristic and may miss details reported outside the abstract.

Recommended queries

Contribution summary

  • In 2022, the second author published a Last Words piece in Computational Linguistics in which he pointed out that, despite the advances in AI up to that point, there were still some problems in natural language processing that on the one…
  • One such problem discussed in that context was text normalization, and a particular subproblem of that, namely number name reading.
  • The piece came out just a few months before the first release of ChatGPT, and needless to say, a lot has happened since then.

Why it matters for eval

  • Abstract shows limited direct human-feedback or evaluation-protocol detail; use as adjacent methodological context.

Researcher checklist

  • Human feedback protocol is explicit

    No explicit human feedback protocol detected.

  • Evaluation mode is explicit

    No clear evaluation mode extracted.

  • Quality control reporting appears

    No calibration/adjudication/IAA control explicitly detected.

  • Benchmark or dataset anchors are present

    No benchmark/dataset anchor extracted from abstract.

  • Metric reporting is present

    No metric terms extracted.