MétaCan
Menu
Back to cohort
Record W6969258641 · doi:10.5284/1099537

18 High Street, Deanshanger, Northamptonshire

2016· article· en· W6969258641 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

VenueArchaeology Data Service · 2016
Typearticle
Languageen
FieldArts and Humanities
TopicHistorical Architecture and Urbanism
Canadian institutionsCanadian Heritage
Fundersnot available
KeywordsAlluviumExcavationTrenchFeature (linguistics)Alluvial plainAggradation

Abstract

fetched live from OpenAlex

The monitoring programme on the groundworks for the present project was divided into three phases. Phase 1 consisted of ground reduction across the entire site. Phase 2 consisted of the altering of the course of an existing stream. Phase 3 consisted of other intrusive groundworks, comprising the excavation of a trench for the disposal of organic matter, together with the footings trenches to the dwelling in Plot 1, the footings for a garden wall in Plot 1 and a soakaway in Plot 1. It was considered that the present investigation had the potential to contribute to a greater understanding of the origins and development of Deanshanger, from the medieval period onwards. The accumulated evidence demonstrates that site was subject to episodes of flooding in the past, alluvial deposits were encountered at a depth of approximately 0.55m below the present ground level. These deposits had been removed on the eastern side of the site and a bank built up to form a wharf on the western side of the canal. The upper layer of the bank contained frequent unburnt coal pieces, indicating that it was used for the delivery of coal. The bank was contained on its western side by a wall constructed from unmortared limestone and sandstone blocks. A possible pit, of 19th century date, and an undated linear feature were also encountered. The linear feature, which lay below the alluvial deposits, may represent a palaeo-channel.

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.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesInsufficient payload (model declined to judge)
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.815
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.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.0010.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0080.001

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.078
GPT teacher head0.243
Teacher spread0.165 · 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