Bibliographic record
Abstract
Abstract Like most reserves issues, the answer depends on the specifics of the project relative to an interpretation of the applicable regulatory guidelines. The US Security and Exchange Commission (SEC) regulation S-X, 4-10 a) states that: "Oil and gas producing activities do not include the extraction of hydrocarbons from shale, tar sands, or coal". Thus, it has been generally accepted that oil derived from processing of mined bitumen cannot be included in petroleum reserves of companies listed on the US stock exchanges. However, the quantities of synthetic oil derived from the upgrading the same bitumen produced out of wellbores using thermal processes are routinely included in reserves disclosures. The logic is that the activities largely duplicate those involved in producing and processing heavy oil. The new Canadian Security Administrators' regulations (NI 51-101), take a different approach: "The intended product of both conventional and non-conventional oil projects is essentially the same – a liquid hydrocarbon. We believe that investors are likely to consider a reporting issuer focused on oil sands to be more comparable to a conventional oil producer than to a hard rock mining issuer. Accordingly, NI 51-101 applies to activities directed at the extraction or production of hydrocarbons from either conventional or non-conventional sources (such as surface mines and in-situ projects)". Which approach provides more clarity for investors? Should the sales product quantities derived from mined and thermally recovered bitumen be treated differently? What would be the international impact of including all bitumen in petroleum reserve estimates and production statistics? This paper presents background and reviews industry practices for the estimation and disclosure of bitumen resources. The issue is of most interest to the Canadian industry; it is forecast that by 2012 over 50% of that nation's crude production may be derived from bitumen.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.012 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.002 | 0.003 |
| Science and technology studies | 0.001 | 0.002 |
| Scholarly communication | 0.005 | 0.006 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.017 | 0.003 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".