MétaCan
Menu
Back to cohort
Record W1457225595

Validating ontologies in informatics systems: approaches and lessons learned for AEC

2014· article· en· W1457225595 on OpenAlex
Tamer E. El-Diraby

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

VenueJournal of Information Technology in Construction · 2014
Typearticle
Languageen
FieldComputer Science
TopicSemantic Web and Ontologies
Canadian institutionsUniversity of Toronto
Fundersnot available
KeywordsBenchmarkingScope (computer science)Computer scienceConstruct (python library)OntologyDimension (graph theory)Data scienceSet (abstract data type)Knowledge managementInformaticsArtificial intelligenceSoftware engineeringEngineeringMathematics
DOInot available

Abstract

fetched live from OpenAlex

In their pursuit to represent a human-savvy machine interpretable model of knowledge, informatics ontologies span three dimensions: philosophy, artificial intelligence, and linguistics. This poses several challenges to ontology validation. Within the scope of knowledge models, four types of validity are relevant: statistical, construct, internal and external. Based on benchmarking some tools and best practices from other domains, a map is proposed to link specify a set of tools to support the handling of four validity types (statistical/conclusion, internal, construct, and external) in each of the three dimensions. The map advocates a debate-based approach in validating the philosophical dimension to allow for innovation and discovery; use of competency questions and automated reasoning tools for the artificial intelligence dimension; and experimenting with lexical analysis tools (especially web contents) for the linguistic dimension. A set of best practices are proposed based on benchmarking other domains. These include falsifying the conceptual frameworks of research methodologies, scope management, iterative development, adequate involvement of experts, and peer review.

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: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.668
Threshold uncertainty score0.288

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.000
Science and technology studies0.0000.000
Scholarly communication0.0000.002
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.047
GPT teacher head0.276
Teacher spread0.228 · 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