MétaCan
Menu
Back to cohort
Record W2943786097 · doi:10.1257/jep.33.2.229

Retrospectives Ricardo on Machinery

2019· article· en· W2943786097 on OpenAlex

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.

Bibliographic record

VenueThe Journal of Economic Perspectives · 2019
Typearticle
Languageen
FieldSocial Sciences
TopicPolitical Economy and Marxism
Canadian institutionsUniversity of Toronto
Fundersnot available
KeywordsOpposition (politics)MillUnemploymentPoliticsNeoclassical economicsEconomicsSubject matterTechnological changeArgument (complex analysis)Positive economicsSociologyLawPolitical scienceHistoryMacroeconomicsEconomic growth

Abstract

fetched live from OpenAlex

We are currently experiencing an outpouring of concern both popular and professional regarding technological unemployment. I shall be discussing an apparent about-turn on the subject by David Ricardo (1772–1823), who at different times, even in different chapters of the same book, and, indeed, even at different places in the same chapter, seemed to be on both sides of the argument as to whether technological unemployment should be a matter for concern. In a chapter entitled “On Machinery,” added to the third edition of his Principles of Political Economy (1821), which comprises volume 1 of his Collected Works (1951–73), Ricardo announced that he had become concerned about the possibility, even likelihood, of technical change detrimental to labour’s interests. However, in the very same “On Machinery” chapter, Ricardo also outlined qualifications to show that there was little need for concern. Ricardo’s opposing messages are reflected in contrasting reactions to the chapter “On Machinery.” Some readers—including Thomas Robert Malthus and J. R. McCulloch—understood it as supporting working-class opposition to machinery. Others—including John Stuart Mill and Sir John Hicks—find therein the answer to such opposition

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.001
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: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.548
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0010.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.012
GPT teacher head0.292
Teacher spread0.280 · 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