MétaCan
Menu
Back to cohort
Record W4410926580 · doi:10.63824/jptsp.v12i1.266

DAMPAK PEMBANGUNAN INFRASTRUKTUR PENGAMAN MUARA SUNGAI BOGOWONTO TERHADAP BAHAYA BANJIR

2025· article· id· W4410926580 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

VenueJURNAL TEKNIK SIPIL PERTAHANAN · 2025
Typearticle
Languageid
FieldComputer Science
TopicMultimedia Learning Systems
Canadian institutionsEncana (Canada)
Fundersnot available
KeywordsGeography

Abstract

fetched live from OpenAlex

Adanya pembangunan Infrastruktur Pengaman Muara Sungai Bogowonto sebagai bangunan pendukung pengamanan Kawasan Strategis Yogyakarta Internasional Airport akan berdampak terhadap Dusun di Desa jangkaran Kecamatan Temon Kabupaten Kulon Progo. Penelitian ini menggunakan jenis penelitian deskriptif kualitatif. Penelitian dilakukan secara analisis deskriptif terhadap data yang diperoleh. Peneliti melakukan eksplorasi terhadap kejadian banjir tahunan di dua Dusun Desa Jangkaran kecamatan Temon Kabupaten Kulon Progo. Data diperoleh melalui wawancara kepada narasumber, pengamatan dan studi dokumen. Makalah ini merupakan upaya perintis untuk mengkaji dampak pembangunan Infrastruktur Pengaman Muara Sungai Bogowonto sebagai bangunan pendukung pengamanan Kawasan Strategis Yogyakarta Internasional Airport terhadap Dusun Pasir Mendit dan Dusun Pasir Kadilangu yang selama ini mengalami banjir setiap tahunnya. Pembangunan Pengaman Muara Sungai Bogowonto yang bertujuan untuk melindungi dan mengamankan Kawasan Strategis YIA berdampak positif terhadap Dusun Pasir Mendit dan Dusun Pasir Kadilangu yang selama ini mengalami banjir tahunan akibat tertutupnya muara Sungai Bogowonto. Pembangunan Jetty pengaman muara sungai tersebut menjadikan kawasan sekitar muara telah terhindar dari banjir.

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.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Science and technology studies, Scholarly communication, Research integrity, Insufficient payload (model declined to judge)
Consensus categoriesMeta-epidemiology (narrow)
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.213
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.001
Meta-epidemiology (narrow)0.0020.002
Meta-epidemiology (broad)0.0020.001
Bibliometrics0.0010.002
Science and technology studies0.0020.001
Scholarly communication0.0020.002
Open science0.0050.002
Research integrity0.0010.003
Insufficient payload (model declined to judge)0.0010.002

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.268
Teacher spread0.256 · 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