data/plwiki_talk/plwiki_talk.md

Polish Wikipedia talk pages (namespaces 1+5) - CC BY-SA 4.0

This slice is rebuilt deterministically from the pinned official Wikimedia dump plwiki-20260901-pages-meta-current (7 sha1-verified shards; https://dumps.wikimedia.org/plwiki/20260901/). Scope is namespaces 1 (article talk) and 5 (project talk); mainspace (ns=0) is covered by the existing wikipedia shard and user-talk (ns=3) is excluded by scope decision (not measured). This is conversational written Polish - editorial disputes, coordination, questions and answers - a register otherwise nearly absent from the corpus.

• Non-redirect talk pages enumerated: 544,591
• Source slice retained after QA/dedup: 43,054
• Proposed records: 43,054
• Proposed tokens: 55,568,733 (cl100k_base proxy)
• Characters: 144,604,697
• License: CC BY-SA 4.0 per record (Wikimedia Terms of Use section 7: https://foundation.wikimedia.org/w/index.php?title=Policy:Terms_of_Use/pl&oldid=584706)
• Immutable source snapshot: https://huggingface.co/datasets/PiotrSty/plwiki-talk-pages/tree/20c74a6da0cbaef5d2a644d0accf7e90262ea24c

Per-record page id, title, namespace, last-revision timestamp and canonical URL are preserved; page history is the contributor-attribution trail. Wikitext is stripped with mwparserfromhell; lines occurring in >=1% of documents are removed as cross-document boilerplate; emails, labelled phones, IP literals, labelled national identifiers and 26-digit account candidates are redacted (pattern redaction is not complete anonymization); exact and near deduplication applied within source. The user-talk namespace (ns=3) is excluded by scope decision; its quality was not measured.

What the texts are (user-generated)

These are user-generated wiki talk pages: discussion between volunteer editors about article content (ns=1, article talk) and about the project itself (ns=5, "Dyskusja Wikipedii" - policies, classifications, deletion debates). Genre: editorial discussion - source requests, wording and naming disputes, style fixes, merge/delete debates, project-wide consultations. Register: informal written Polish with typos, wiki jargon ("WP:OR", "SDU"), signed comments (user name + timestamp). Not OCR'd, not machine-translated. Record model: one whole talk page; comments are not split.

Time span: per-record created is the dump last-revision date (2003-02-13 – 2026-09-01 across 43,054 records); the talk activity itself spans the whole life of plwiki (ns split: 41,828 article-talk pages, 1,226 project-talk pages).

Scrubber and residual-PII spot check

Scrubber that ran: pattern redaction in src/build_plwiki_talk_pl.py - e-mail, labelled phone (telefon/tel./phone), IPv4, parsed IPv6 (incl. compressed notation), labelled PESEL/NIP/REGON, 26-digit account candidates -> [REDACTED:*]. This is not SlayerLab/NERGAL; these are user-generated talk pages, so the shard must be re-run through NERGAL before it is admitted to a release.

Residual-PII spot check (deterministic sample of 60 records, seed 20260928): 25 [REDACTED:IP] placeholders remain as evidence of the applied redaction (including unregistered editors' signatures); the single long-digit-run hit is an academic DOI citation (10.1017/9781108668675.006) - not PII; all other residual classes (26-digit runs, IBAN-like, unlabelled IPs, e-mail-like incl. obfuscated "at"/"malpa" forms, ul./al./os. street cues, GG/ICQ/Skype, PESEL mentions) have 0 hits. Manual reading of 8 sampled records found only public wiki attribution and editorial discussion - no private personal data. Residual risk low but non-zero (60 of 43,054 records, 0.14%), which is why the NERGAL pass stays a release gate.

Inclusion argument

What this adds that wikipedia does not: the editorial process around the articles - talk pages where editors argue about sources, wording, naming, merges and deletions. That is conversational, multi-voice, disagreement-laden Polish; the wikipedia shard holds only the finished encyclopedic prose. The namespace partition is exact: wikipedia = ns 0, this slice = ns 1+5, plwiki_user_talk (PR #40) = ns 3 - no page is in two slices, and the text overlap numbers below quantify what still repeats across them.

Text overlap with the wikipedia / plwiki_user_talk shards (review audit)

Measured post-build by normalized exact-line and exact-paragraph containment (64-bit blake2b; lines >= 30 chars, paragraphs >= 100 chars; exact-verbatim only):

• vs wikipedia (ns 0): 418 of 567,171 talk lines match (75,163 chars = 0.053% of this slice's line chars); 1 paragraph (271 chars). Verbatim article quoting in talk pages is negligible at this unit size.
• vs plwiki_user_talk (ns 3): 5,556 lines match (1,207,378 chars = 0.85%); 1,111 paragraphs (547,695 chars = 0.39%); 1,965 of 43,054 records (4.6%) contain at least one matched line. The matched lines are almost all page-unique (4,941 of 5,138 distinct matched lines occur on exactly one talk page) - genuine thread fragments mirrored between article talk and user talk, not template duplication.

Integration gate: cross-shard verbatim dedup at integration would move ~0.9% of chars; no other treatment needed. Method and numbers are in the review thread (overlap_check_pr36.py, overlap_pr36.json).

Limitations: talk pages are informal (typos, edit disputes, occasional vandalism); comments may quote article text (measured at review: 0.053% of chars match the wikipedia shard verbatim at line level; 0.85% matches plwiki_user_talk, almost all page-unique thread fragments); Record model is a whole talk page; comments are not split.