MétaCan
Menu
Back to cohort
Record W2203597119

Mining common morphological fragments from process event logs

2014· article· en· W2203597119 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

VenueComputer Science and Software Engineering · 2014
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicBusiness Process Modeling and Analysis
Canadian institutionsSimon Fraser UniversityToronto Metropolitan University
Fundersnot available
KeywordsComputer scienceProcess miningCode refactoringProcess (computing)Event (particle physics)Data miningBusiness process discoveryProcess modelingWork in processSoftware engineeringArtificial intelligenceBusiness processBusiness process managementBusiness process modelingProgramming languageSoftwareEngineering
DOInot available

Abstract

fetched live from OpenAlex

Many organizations have implemented their organizational processes within integrated information systems using formal process models. These processes, which have been implemented in different organizations can share significant amount of similarities. Analysis and mining of these processes for identifying similarities can lead to valuable insight for the organizations. There has already been work on mining process models from event logs for an individual organization. The objective of this paper is, however, to detect and extract common process fragments from a family of processes that may not have been executed within the same application/organization. These identified common fragments can be used as building blocks of future applications or be used for refactoring existing applications. To this end, we first provide a precise definition of process fragments. We define morphological fragments as operationally identical fragments. We then propose an algorithm for extracting morphological fragments from process event logs. We discuss the relative performance of our proposed algorithm and its applicability in practice.

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: Empirical · Consensus signal: Empirical
Teacher disagreement score0.579
Threshold uncertainty score0.605

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.0000.000
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.011
GPT teacher head0.212
Teacher spread0.201 · 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