MétaCan
Menu
Back to cohort
Record W2782779765

Using IBM watson cloud services to build natural language processing solutions to leverage chat tools

2017· article· en· W2782779765 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 · 2017
Typearticle
Languageen
FieldComputer Science
TopicSpeech and dialogue systems
Canadian institutionsIBM (Canada)
Fundersnot available
KeywordsIBMWatsonComputer scienceLeverage (statistics)Cloud computingWorld Wide WebCognitive computingMultimediaData scienceArtificial intelligenceCognitionOperating system
DOInot available

Abstract

fetched live from OpenAlex

Chat tools are changing the way companies engage with customers. On the one hand, these tools have tremendous benefits. They can provide an excellent experience for customers who have questions or who are having trouble. Also, analyzing historical chat conversations can help a company understand customer needs and make better business decisions. On the other hand, keeping up with a large volume of live chat messages can be difficult. And easy-to-use tools for handling those messages - using natural language processing (NLP) techniques, for example, without having to build components by hand - have not been generally available. This paper describes our experience using IBM Watson cloud services to build cognitive solutions for processing chat messages. In this paper, we share five lessons we learned while building our solutions.

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 categoriesScholarly communication
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.939
Threshold uncertainty score0.998

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.0030.002
Open science0.0020.002
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.265
Teacher spread0.238 · 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