MétaCan
Menu
Back to cohort
Record W1950860289 · doi:10.3233/ida-2008-12205

Bridging the gap between data mining and decision support: A case-based reasoning and ontology approach

2008· article· en· W1950860289 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

VenueIntelligent Data Analysis · 2008
Typearticle
Languageen
FieldComputer Science
TopicData Mining Algorithms and Applications
Canadian institutionsUniversité du Québec à Trois-Rivières
Fundersnot available
KeywordsBridging (networking)OntologyComputer scienceDecision support systemData scienceData miningKnowledge managementEpistemology

Abstract

fetched live from OpenAlex

Nowadays, decision makers invariably need to use decision support technology (DS) such as data mining (DM) methodologies and tools in order to tackle complex decision making problems. However the successful application of DM technology requires that one possess specific DM decision-making skills. F or instance, the effective application of a data mining process is littered with many difficult and technical decisions (i.e. data cleansing, feature transformations, algorithms, parameters, evaluation, etc.) In essence, this contentious problem and burden for decision makers clearly stems from a poor DM-DS integration. As a result, we have strived to improve on this problem by proposing an intelligent DM assistant that can potentially empower decision makers to better leverage DM technology and achieve their intended business objectives. Nonetheless, as this paper will strive to demonstrate, the realization of an intelligent data mining assistant for the decision maker or non-specialist data miner is a challenging and complex endeavour. Hence, in what follows we present the key design considerations (i.e. knowledge representation and reasoning, knowledge elicitation and reuse efforts, etc.) that were addressed during the implementation of a hybrid data mining assistant, based on the case-based reasoning (CBR) paradigm and the use of a formal OWL-DL ontology.

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.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.991
Threshold uncertainty score0.520

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0010.000
Scholarly communication0.0000.001
Open science0.0030.003
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.157
GPT teacher head0.343
Teacher spread0.186 · 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