MétaCan
Menu
Back to cohort
Record W3080090093 · doi:10.5539/ilr.v9n1p77

Producer Liability for AI-Based Technologies in the European Union

2020· article· en· W3080090093 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.

venuePublished in a venue whose home country is Canada.
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

VenueInternational Law Research · 2020
Typearticle
Languageen
FieldComputer Science
TopicLaw, AI, and Intellectual Property
Canadian institutionsnot available
Fundersnot available
KeywordsLiabilityStrict liabilityProduct liabilityLegal liabilityLimited liability partnershipBusinessEconomicsFinance

Abstract

fetched live from OpenAlex

The manufacturer's liability for defective products has remained almost unmodified since 1985 when Directive 85/374/EEC (=PLD) was enacted. Perhaps new technology based on artificial intelligence (=AI) could bring about a turning point in the regulation if concepts such as "product" and "defect" or aspects such as "grounds of liability", the so-called "development risks defense", and the "solidarity" are reconsidered. The Group of Experts on Liability and New Technologies (=NTF), in its “Liability for AI and other emerging digital technologies” Report, recommends, inter alia, the regulation of two different civil liability regimes: strict liability and fault-based liability. Thus, it will be necessary to determine precisely the cases to which these regimes apply and how to deal with “uncertain causation”. The alleviation of the victim’s burden of proof should be considered. From the various documents being published, it appears that the producer’s strict liability will remain as the main liability rule, but it will be combined -as the NFT suggests- in the case of the breach of a duty of care with a fault-based liability rule. This approach leaves some open questions, i.e., how to properly combine both grounds of liability in the domain of products that cause damages. In my view, the liability regime suggested by the NTF is far more complicated that the regime which distinguishes three types of defects that are often stressed: the defect of design, the defect of manufacturing, and the defect of information.

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.004
metaresearch head score (Gemma)0.002
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.993
Threshold uncertainty score0.488

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0040.002
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.0030.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.157
GPT teacher head0.375
Teacher spread0.218 · 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