MétaCan
Menu
Back to cohort
Record W2996207569 · doi:10.16995/dm.84

Cartography and Code: Incorporating Automation in the Exploration of Medieval Mappaemundi

2019· article· en· W2996207569 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.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueDigital Medievalist · 2019
Typearticle
Languageen
FieldArts and Humanities
TopicLinguistics and language evolution
Canadian institutionsnot available
Fundersnot available
KeywordsFolioToponymyVisualizationIdeologyCode (set theory)Source codeCartographyComputer scienceGeographyHistoryProgramming languageArt historyArchaeologyData miningLawPolitical science

Abstract

fetched live from OpenAlex

The study of medieval mappaemundi has traditionally relied on comparative analysis as one of the methods to examine and identify possible centres of map production, common sources and conceptions of space and place, as well as possible social, institutional, ideological, and economic connections between maps. The comparison of place names between medieval mappaemundi is one of the ways scholars can compare toponyms across maps, but this has, until now, been conducted by hand, usually on a case by case study. This paper introduces a new digital tool called veccompare, designed to facilitate an in-depth study of the relationships between mappaemundi vis à vis their textual content. As a case study, veccompare has been used for the comparison of two Psalter maps. Veccompare’s output report and visualization of data has led to a better understanding of the Psalter maps’ close physical proximity, namely on the same folio in the same manuscript. It may be pursuant not to a direct, one-to-one, model-derivative type of relationship between the maps, but rather to an indirect relationship stemming from a common textual source used by both mapmakers.

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 categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.606
Threshold uncertainty score0.224

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.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.027
GPT teacher head0.239
Teacher spread0.212 · 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