MétaCan
Menu
Back to cohort
Record W3043060821 · doi:10.5194/agile-giss-1-14-2020

Uncovering spatiotemporal biases in place-based social sensing

2020· article· en· W3043060821 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

VenueAGILE GIScience Series · 2020
Typearticle
Languageen
FieldSocial Sciences
TopicHuman Mobility and Location-Based Analysis
Canadian institutionsMcGill University
Fundersnot available
KeywordsCategorizationRecreationData scienceComputer scienceService (business)Data collectionWorld Wide WebArtificial intelligenceSociologyEcology

Abstract

fetched live from OpenAlex

Abstract. Places can be characterized by the ways that people interact with them, such as the times of day certain place types are frequented, or how place combinations contribute to urban structure. Intuitively, schools are most visited during work day mornings and afternoons, and are more likely to be near a recreation center than a nightclub. These temporal and spatial signatures are so specific that they can often be used to categorize a particular place solely by its interaction patterns. Today, numerous commercial datasets and services are used to access required information about places, social interaction, news, and so forth. As these datasets contain information about millions of the same places and the related services support tens of millions of users, one would expect that analysis performed on these datasets, e.g., to extract data signatures, would yield the same or similar results. Interestingly, this is not always the case. This has potentially far reaching consequences for researchers that use these datasets. In this work, we examine temporal and spatial signatures to explore the question of how the data acquiring cultures and interfaces employed by data providers such as Google and Foursquare, influence the final results. We approach this topic in terms of biases exhibited during service usage and data collection.

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.001
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Qualitative · Consensus signal: Qualitative
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.240
Threshold uncertainty score0.994

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0010.001
Scholarly communication0.0000.001
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.055
GPT teacher head0.306
Teacher spread0.251 · 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