MétaCan
Menu
Back to cohort
Record W2887329105 · doi:10.21474/ijar01/7375

THE CONSISTENCY OF LEGAL ANALYSIS FOR DOCUMENT PLANNING AND IMPLEMENTATION OF RURAL FINANCIAL MANAGEMENT BASED ON WORK PROGRAM IN REGENT OF NORTH BOLAANG MONGONDOW.

2018· article· en· W2887329105 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

VenueInternational Journal of Advanced Research · 2018
Typearticle
Languageen
FieldSocial Sciences
TopicLocal Governance and Development
Canadian institutionsEncana (Canada)
Fundersnot available
KeywordsWork (physics)Government (linguistics)Plan (archaeology)ParagraphRevenueDevelopment planConsistency (knowledge bases)BusinessProcess (computing)Public administrationEconomic growthFinancePolitical scienceEngineeringGeographyComputer scienceEconomicsCivil engineering

Abstract

fetched live from OpenAlex

In Law Number 6 of 2014 article 81 paragraph (1) it is explained that the Village Development is carried out in accordance with the Village Government Work Plan. From the explanation of those articles shows that, development done in the Village must be done in accordance with the planning that has been in the previous arrangement, it is intended that development planning and implementation are integrated. The preparation of this work plan helps the village government in the implementation stage of the activity, so that the activities carried out can provide benefits for the village community. In the village development planning process, the village government should prepare three (3) planning documents namely the Village Mid Term Development Plan, the Village Government Work Plan, and the Village Revenue and Expenditure Budget. In accordance with the data that researchers have obtained several villages in Bolaang Mongondow North District in making the development planning documents of the village always reap various technical problems. So that impact on the process of realization of the implementation.

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.002
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.521
Threshold uncertainty score0.151

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
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.0000.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.032
GPT teacher head0.450
Teacher spread0.418 · 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