Browse State-of-the-Art › Document Dating

Document Dating

2 papers with code · 2 benchmarks · 1 dataset archive 2025-07-28

Natural Language Processing

Document Dating is the problem of automatically predicting the date of a document based on its content. Date of a document, also referred to as the Document Creation Time (DCT), is at the core of many important tasks, such as, information retrieval, temporal reasoning, text summarization, event detection, and analysis of historical text, among others.

For example, in the following document, the correct creation year is 1999. This can be inferred by the presence of terms 1995 and Four years after.

Swiss adopted that form of taxation in 1995. The concession was approved by the govt last September. Four years after, the IOC….

Description from NLP Progress

Description from the archive archive 2025-07-28.

Benchmarks archive 2025-07-28

2 leaderboard tables shown for this task, 2 with rows (a “benchmark” on this site is a table with at least one row, as on /sota), ordered by row count. “Best model” is the first row in the archive's own order at snapshot; nothing is re-ranked here and metric direction is not recorded in the archive. PwC's Trend sparklines are not in the archive, so that column is omitted.

DatasetBest model (first row in archive order)PaperCodeSyntologyCompare
APW (3 rows) NeuralDater Dating Documents using Graph Convolution Networks code — Compare
NYT (3 rows) NeuralDater Dating Documents using Graph Convolution Networks code — Compare

Syntology column: samples harvested from the paper's repositories and executed on synthesized fixtures; “ran” is not a correctness claim and does not order the table. Each line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the row's paper, the line starts with that repository's state (“official” is the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from. A dash means no Syntology record for that paper, not a recorded non-run. Each “ran” line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.

Libraries

Not in the archive: the export carries no per-task library table, so there is nothing to show at snapshot 2025-07-28.

Datasets archive 2025-07-28

1 dataset whose archive record lists this task, ordered by the archive's paper count.

Subtasks archive 2025-07-28

No subtask under this task in the archive's task tree.

Parent tasks archive 2025-07-28

Papers archive 2025-07-28

archive papers tagged: 9 · with a code link: 2 · where Syntology ran a sample: 0 (0 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran: none of the 9 tagged papers has a Syntology run on record

Page 1 of 1: papers 1 to 9 of 9, in archive order: by repositories listed in the archive (most first), then newest first, not by stars (the archive holds no stars, so PwC's “Social” and “Latest” sorts cannot be reproduced). Papers that list no repository come after every paper that lists one.

Papers without a page here are shown as plain text. A Syntology line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the figure “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code); hover it for the repositories the samples that ran came from.

  • 1 Feb 2019 1 repository listed
    While existing approaches for these tasks assume accurate knowledge of the document date, this is not always available, especially for arbitrary documents from the Web.
  • 21 Jan 2019 1 repository listed
    Knowledge of the creation date of documents facilitates several tasks such as summarization, event extraction, temporally focused information extraction etc.
  • Is text normalization relevant for classifying medieval charters?
    29 Aug 2024 0 repositories listed
    This study examines the impact of historical text normalization on the classification of medieval charters, specifically focusing on document dating and locating.
  • Towards Effective Time-Aware Language Representation: Exploring Enhanced Temporal Understanding in Language Models
    4 Jun 2024 0 repositories listed
    In the evolving field of Natural Language Processing, understanding the temporal context of text is increasingly crucial.
  • Timestamping Documents and Beliefs
    9 Jun 2021 0 repositories listed
    Most of the textual information available to us are temporally variable.
  • Dating Ancient texts: an Approach for Noisy French Documents
    1 May 2020 0 repositories listed
    Automatic dating of ancient documents is a very important area of research for digital humanities applications.
  • Graph Convolutional Network with Sequential Attention For Goal-Oriented Dialogue Systems
    1 May 2019 0 repositories listed
    Domain specific goal-oriented dialogue systems typically require modeling three types of inputs, viz., (i) the knowledge-base associated with the domain, (ii) the history of the conversation, which is a sequence of…
  • 1 Jul 2014 0 repositories listed
    A large number of mainstream applications, like temporal search, event detection, and trend identification, assume knowledge of the timestamp of every document in a given textual collection.
  • 1 Jul 2012 0 repositories listed

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