West Front Footpath Re-laying Works, Hampton Court Palace
Bibliographic record
Abstract
In April 2023, a path which runs from Barge Walk diagonally across the West Front towards the Great Gate House at Hampton Court Palace was re-laid as part of an overarching ambition to improve accessibility into the palace during busy periods. The work was covered under the Standing Clearances agreement between Historic Royal Palaces and Historic England and did not require Scheduled Monument Consent. As part of the installation works, a shallow 0.2m-0.3m excavation was undertaken with a mechanical excavator with Historic Royal Palaces' Archaeologist in attendance. At the discovery of archaeological remains, the maintenance works were paused to allow for further archaeological investigation and recording. During this project, the remains of a ragstone surface were uncovered. The remains are believed to be one of three causeways installed in 1699, which once formed part of the original patte-d'oie formation of roadways leading to the West Front entrance of the palace installed as part of William III and Mary II's reconfiguration. However, it seems that this central branch of roadways was quite quickly reburied, seemingly going out of use by the 1730's. Several finds were uncovered from the causeway itself and from the overlying soil. Though most finds were of a tertiary or secondary nature, the few objects immediately associated with the ragstone surface do align with an early 18th century date.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.005 | 0.001 |
| Scholarly communication | 0.004 | 0.001 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.146 | 0.013 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".