MétaCan
Menu
Back to cohort
Record W2057530735 · doi:10.1021/ef100765u

Recovery of Bitumen from Utah Tar Sands Using Ionic Liquids

2010· article· en· W2057530735 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.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueEnergy & Fuels · 2010
Typearticle
Languageen
FieldChemistry
TopicPetroleum Processing and Analysis
Canadian institutionsnot available
Fundersnot available
KeywordsOil sandsAsphaltSlurryMixing (physics)AsphalteneToluenetar (computing)Ionic liquidSolventChemical engineeringViscosityEnvironmental scienceGeologyMineralogyChemistryMaterials scienceOrganic chemistryEnvironmental engineeringComposite materialCatalysis

Abstract

fetched live from OpenAlex

Hot or warm water processes are used to extract bitumen from Canadian oil or tar sands. The application of these methods to the processing of tar sand deposits found in the Western United States, notably Utah, has not been commercially successful, however, because of the consolidated nature of the deposits and the high viscosity of the bitumen. It is demonstrated here that a previously developed method employing ionic liquids (ILs) together with a nonpolar solvent such as toluene can effect a separation at ambient temperatures (∼25 °C), although with greater difficulty than Canadian oil sands. Essentially, a multiphase system consisting of a sand and clay slurry, an ionic liquid layer, and an organic layer containing the bitumen can be formed by simply mixing the components. More than 90% of the bitumen is released from the sand, but only in successive extractions. Water is not used in this stage of the separation, but relatively small amounts are used to separate entrained IL from the sand and clays.

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.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.015
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0020.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.009
GPT teacher head0.230
Teacher spread0.221 · 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