Verified claim · AI-ML · 100% confidence
Byte-Pair Encoding (BPE) for Neural Machine Translation introduced in paper: Neural Machine Translation of Rare Words with Subword Units (Sennrich et al., 2015).
Last verified 2026-05-16 · Methodology veritas-v0.1 · e942c93d70a4dab2
SourceScore rates how reliable a source is to cite — for AI answers and research. This is one verified claim from the catalog.
Structured fields
- Subject
- Byte-Pair Encoding (BPE) for Neural Machine Translation
- Predicate
introduced_in_paper- Object
- Neural Machine Translation of Rare Words with Subword Units (Sennrich et al., 2015)
- Confidence
- 100%
- Tags
- bpe · tokenization · foundational · sennrich · 2015 · acl · nmt
Sources (2)
[1] preprint · arXiv (Sennrich, Haddow, Birch) · 2015-08-31
Neural Machine Translation of Rare Words with Subword Units“We introduce a simpler and more effective approach, making the NMT model capable of open-vocabulary translation by encoding rare and unknown words as sequences of subword units.”
[2] peer reviewed · Association for Computational Linguistics · 2016-08-07
Neural Machine Translation of Rare Words with Subword Units (ACL 2016)
Cite this claim
Ready-to-paste citation (Markdown / plain text):
Byte-Pair Encoding (BPE) for Neural Machine Translation introduced in paper: Neural Machine Translation of Rare Words with Subword Units (Sennrich et al., 2015). — SourceScore Claim e942c93d70a4dab2 (verified 2026-05-16). https://sourcescore.org/api/v1/claims/e942c93d70a4dab2.jsonEmbed this claim
Drop this iframe into any blog post, docs page, or knowledge base. The widget renders the signed claim + primary source + click-through to this canonical page. CC-BY 4.0; attribution included.
<iframe src="https://sourcescore.org/embed/claim/e942c93d70a4dab2/" width="100%" height="360" frameborder="0" loading="lazy" title="Byte-Pair Encoding (BPE) for Neural Machine Translation introduced in paper: Neural Machine Translation of Rare Words with Subword Units (Sennrich et al., 2015)."></iframe>Preview: open in new tab
Related claims
Other verified claims sharing tags with this one — useful for LLM retrieval graphs and citation discovery.
Byte-Pair Encoding (BPE) for NMT introduced in paper: Neural Machine Translation of Rare Words with Subword Units (Sennrich et al., 2015).
aede848e23c8de8e · 100% confidence · shares 5 tags (bpe, tokenization, foundational…)
ResNet (Residual Networks) introduced in paper: Deep Residual Learning for Image Recognition (He et al., 2015).
4f55f77c4bfb316e · 100% confidence · shares 2 tags (foundational, 2015)
SentencePiece tokenizer introduced in paper: SentencePiece: A simple and language independent subword tokenizer and detokenizer for Neural Text Processing (Kudo & Richardson, 2018).
0d47bb8eb637a2e4 · 100% confidence · shares 2 tags (tokenization, foundational)
Batch Normalization introduced in paper: Batch Normalization: Accelerating Deep Network Training by Reducing Internal Covariate Shift (Ioffe & Szegedy, 2015).
56c451642ab41e68 · 100% confidence · shares 2 tags (foundational, 2015)
BLEU score introduced in paper: BLEU: a Method for Automatic Evaluation of Machine Translation (Papineni et al., 2002).
bf5bdd9756278449 · 100% confidence · shares 2 tags (foundational, acl)
Frequently asked questions
Is the claim "Byte-Pair Encoding (BPE) for Neural Machine Translation introduced in paper: Neural Machine Translation of Rare Words with Subword Units (Sennrich et al., 2015)." verified?
Yes — SourceScore verified this claim with 100% confidence as of 2026-05-16. The verification uses 2 primary sources cross-referenced against the SourceScore methodology (version veritas-v0.1). Full source list + signed JSON envelope linked below.
What is the evidence for "Byte-Pair Encoding (BPE) for Neural Machine Translation introduced in paper: Neural Machine Translation of Rare Words with Subword Units (Sennrich et al., 2015)."?
Evidence comes from 2 primary sources: arXiv (Sennrich, Haddow, Birch), Association for Computational Linguistics. Each source is listed below with verbatim excerpts and URLs. The signed JSON envelope at https://sourcescore.org/api/v1/claims/e942c93d70a4dab2.json includes an HMAC-SHA256 signature for audit verification.
When was this claim last verified by SourceScore?
Last verified 2026-05-16 under methodology version veritas-v0.1. The signed JSON envelope is dated and cryptographically signed for audit trail. Re-verification cadence depends on the claim type and source freshness.
How can I cite this SourceScore claim in my code or article?
Fetch the signed JSON envelope from https://sourcescore.org/api/v1/claims/e942c93d70a4dab2.json which includes the verbatim claim, primary sources, confidence, methodology version, last-verified date, and HMAC-SHA256 signature for audit. The CC-BY-4.0 license permits commercial use with attribution to SourceScore.
Use this claim in your code
Fetch this signed envelope from your application. The response includes the verbatim excerpt, primary source URLs, and an HMAC-SHA256 signature you can verify locally for audit trails.
cURL
curl https://sourcescore.org/api/v1/claims/e942c93d70a4dab2.jsonJavaScript / TypeScript
const r = await fetch("https://sourcescore.org/api/v1/claims/e942c93d70a4dab2.json");
const envelope = await r.json();
console.log(envelope.claim.statement);
// "Byte-Pair Encoding (BPE) for Neural Machine Translation introduced in paper: Neural Machine Translation of Rare Words with Subword Units (Sennrich et al., 2015)."Python
import httpx
r = httpx.get("https://sourcescore.org/api/v1/claims/e942c93d70a4dab2.json")
envelope = r.json()
print(envelope["claim"]["statement"])
# "Byte-Pair Encoding (BPE) for Neural Machine Translation introduced in paper: Neural Machine Translation of Rare Words with Subword Units (Sennrich et al., 2015)."LangChain (retrieve-then-cite)
from langchain_core.tools import tool
import httpx
@tool
def get_byte_pair_encoding_bpe_for_neural_machine_translation_fact() -> dict:
"""Fetch the verified SourceScore claim for Byte-Pair Encoding (BPE) for Neural Machine Translation."""
r = httpx.get("https://sourcescore.org/api/v1/claims/e942c93d70a4dab2.json")
return r.json()