polish-dynaword / data /sejm_interpellations /sejm_interpellations.md
ppuzio's picture
Add source: sejm_interpellations — 10th-term written Q&A (#24)
5c05a34
|
Raw History Blame
4.71 kB

sejm_interpellations

Interpelacje i zapytania pisemne z 10. kadencji Sejmu, wraz z odpowiedziami ministerstw dostępnymi jako HTML.

Dataset description

Licensing — traceable basis

Official parliamentary materials are excluded from copyright under Polish Copyright Act art. 4 pkt 2 (https://eli.gov.pl/api/acts/DU/2025/24/text/O/D20250024.pdf). Reuse of public-sector information is governed by the Polish Open Data Act arts. 2(12), 5, 14 and 17 (https://eli.gov.pl/api/acts/DU/2023/1524/text.html). Same basis as the shipped sejm_api shard. No Creative Commons grant is asserted.

What the texts are

Written questions from MPs to ministers (interpellations, writtenQuestions) and the ministry replies that the API serves as HTML. Spoken floor speeches are not included — those are sejm_api (2023–) and #18 (2011–2022). Same kadencja, different genre.

PDF-only replies (onlyAttachment: true) and keyless prolongation stubs are skipped. Term 9 listed X-Total-Count: 0 on both collections at fetch time and is not in this shard. Terms 7–8 were not fetched (PPC already covers interpellations through 2019).

Provenance and reproducibility

python3 src/fetch_sejm_interpellations.py --out ~/speakleash --terms 9,10 --workers 4
python3 src/build_dynaword.py --sources sejm_interpellations --speakleash-dir ~/speakleash --out .

src/fetch_sejm_interpellations.py pulls HTML /body endpoints, strips header chrome (nr / recipient / title / signatory / date) into meta, then runs pattern PII redaction (the scrub_pii pass from #20 at build time — phones → [Telefon]; e-mail / PESEL / NIP / REGON / IBAN → [PII]). That in-repo scrubber was removed in #38; PII now goes through SlayerLab/NERGAL and this shard must be re-run through NERGAL before it is admitted to a release (it quotes constituency casework naming private persons). Names of public officials stay. build_dynaword.py applies the usual gates (strip, < 200 chars, Polish diacritic ratio, exact sha1).

Why include it

The corpus already has spoken Sejm (parliamentary, sejm_api). This adds the written Q&A register for the current term: longer, formal, ministry-voiced replies that do not appear in the speech shards — the argumentative question/answer pair is a document type the corpus otherwise lacks entirely. Caveats for downstream users: single term (10th, 2023-11-15 – 2026-09-03), and interpellations quote constituency casework that can name private citizens (see Privacy below — a NERGAL pass is a release gate).

Statistics

Measure Value
JSONL rows read 26,503
Exact duplicate texts removed 553
Documents published 25,950
Characters 78,607,831
Tokens (cl100k_base proxy) 28,180,895
Documents with author attribution 25,950

JSONL mix before dedup: 19,413 interpellations, 3,889 written questions, 2,730 interpellation replies, 471 written-question replies. All term 10.

Filters applied (build_dynaword.py)

  • drop documents < 200 chars: 0
  • drop non-Polish (diacritic ratio): 0
  • exact sha1 dedup: 553
  • OCR alpha-ratio: 0
  • read 26,503 → kept 25,950

Sample

Question (author Daniel Milewski):

Szanowny Panie Ministrze,

latem 2022 roku na podlaskiej części granicy z Białorusią ukończono zaporę
fizyczną, czyli 5,5-metrowy płot ze stalowych przęseł zwieńczony drutem
żyletkowym. Ogrodzenie stoi na 186 kilometrach. […]

Reply (author sekretarz stanu w Ministerstwie Spraw Zagranicznych Władysław Teofil Bartoszewski):

Szanowny Panie Marszałku,

w odpowiedzi na zapytanie poselskie nr 3472 pana posła Bronisława Foltyna
w sprawie Instytutu Polskiego w Szwajcarii, uprzejmie informuję, co
następuje. […]

Privacy and limitations

Regex PII scrub at fetch time is not a guarantee of zero personal data. Constituency casework in interpellations can name private persons; those names are left in (officials acting in capacity are not treated as PII). Downstream users must review applicable privacy and source terms. Per AGENTS.md the shard must be re-run through SlayerLab/NERGAL before release; merge with release: None is fine meanwhile.