MétaCan
Menu
Back to cohort
Record W4220868598 · doi:10.33137/utjph.v3i2.36174

A Strategy Design Analysis of the Toronto Poverty Reduction Strategy

2022· article· en· W4220868598 on OpenAlex
Shaurya Gupta, Marian Kelly, Rachel Ginsberg, Hiba Ahmed, Nuzha Hafleen, Emily Taylor, Robert Schwartz

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueUniversity of Toronto Journal of Public Health · 2022
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicGlobal Public Health Policies and Epidemiology
Canadian institutionsPublic Health OntarioUniversity of Toronto
Fundersnot available
KeywordsPovertyStrengths and weaknessesPoverty reductionGovernment (linguistics)PrioritizationCorporate governanceDesign strategyPhase (matter)Political sciencePublic economicsEconomic growthBusinessProcess managementEconomicsPsychologyManagement

Abstract

fetched live from OpenAlex

Poverty reduction strategies have become a popular policy instrument for addressing poverty across various levels of government. In 2015, the City of Toronto launched phase one of its own municipal poverty reduction strategy, which ran from 2015 to 2018. The following commentary uses strategy design principles to examine the strengths and weaknesses of phase one of the Toronto Poverty Reduction Strategy (TPRS) based on interviews conducted with four key stakeholders involved in the strategy’s design and implementation. Joined-up governance and public participation were both identified as design strengths of the TPRS, while a lack of prioritization and funding were identified as challenges to effective implementation. As governments across Canada and the world search for feasible, acceptable, and effective ways to reduce and alleviate poverty and other health-related issues. strategy design principles provide a valuable framework for analyzing the complex processes which contribute to a strategy’s success or failure.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.005
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.419
Threshold uncertainty score0.998

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0050.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0020.000

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.

Opus teacher head0.073
GPT teacher head0.288
Teacher spread0.215 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it