Browse State-of-the-Art › Japanese Word Segmentation

Japanese Word Segmentation

3 papers with code · 1 benchmark · 0 datasets archive 2025-07-28

Natural Language Processing

Benchmarks archive 2025-07-28

1 leaderboard table shown for this task, 1 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
BCCWJ (3 rows) LATTE (Linguistic units, lattices, PTMs, GNNs) LATTE: Lattice ATTentive Encoding for Character-based Word Segmentation 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

No dataset record in the archive lists this task.

Subtasks archive 2025-07-28

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

Papers archive 2025-07-28

archive papers tagged: 7 · with a code link: 3 · 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 7 tagged papers has a Syntology run on record

Page 1 of 1: papers 1 to 7 of 7, 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 Jun 2023 2 repositories listed
    Our model employs the lattice structure to handle segmentation alternatives and utilizes graph neural networks along with an attention mechanism to attentively extract multi-granularity representation from the lattice…
  • 1 May 2022 1 repository listed
    Thinking in reverse, CWS can also be viewed as a process of grouping a sequence of characters into a sequence of words.
  • 1 Jun 2019 1 repository listed
    Neural network models have been actively applied to word segmentation, especially Chinese, because of the ability to minimize the effort in feature engineering.
  • A Text Editing Approach to Joint Japanese Word Segmentation, POS Tagging, and Lexical Normalization
    1 Nov 2021 0 repositories listed
    Lexical normalization, in addition to word segmentation and part-of-speech tagging, is a fundamental task for Japanese user-generated text processing.
  • Character Feature Engineering for Japanese Word Segmentation
    3 Oct 2019 0 repositories listed
    On word segmentation problems, machine learning architecture engineering often draws attention.
  • A Japanese Word Segmentation Proposal
    1 Jul 2019 0 repositories listed
    Current Japanese word segmentation methods, that use a morpheme-based approach, may produce different segmentations for the same strings.
  • 23 Sep 2017 0 repositories listed
    This study presents a Long Short-Term Memory (LSTM) neural network approach to Japanese word segmentation (JWS).

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