Kauno pavieto įsijungimo į 1794 m. sukilimą akto ypatybės
Bibliographic record
Abstract
The uprising of 1794 demonstrated certain features of general confederation which was typical in the Polish-Lithuanian Commonwealth. Specifically, when a group of persons or representatives of a certain district established an act which proclaimed certain goals (for example, the rights of nobility, the defence of the beliefs of a certain confession, etc.), the representatives of other districts would also announce an act supporting the aims of the initiators and join them as equal members. The first official document of the rebels became the act of uprising of the citizens of Kraków district (vaivadija) issued in Kraków on the 24th of March. The administrative districts of Poland and Lithuania were officially joining the uprising in the approval of the act. However, due to particular reasons, after the liberation of Vilnius, the rebels of Lithuania declared a separate act of uprising of the Grand Duchy of Lithuania on the 24th of April, 1794. Although the districts of the Grand Duchy of Lithuania bordering with Poland joined the Kraków act, the majority of districts (pavietai) expressed approval to the Vilnius act. Kaunas was one of the first districts (pavietas) which officially joined the uprising. The Kaunas district act of joining the uprising declared on the 30th of April, 1794, unconditionally acknowledged the Vilnius act. Apart from the official part, the Kaunas act listed the actions implemented in support of uprising and presented a program of further moves. Within... [to full text]
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.002 | 0.001 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.000 | 0.002 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.024 | 0.011 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".