Description: A Starship food delivery robot deployed by Oregon State University reportedly failed to cross the railroad, becoming stranded, and ending up being struck by an oncoming freight train.
推定: Starship Technologiesが開発し、Oregon State Universityが提供したAIシステムで、Oregon State University と freight train crewに影響を与えた
インシデントのステータス
インシデントID
176
レポート数
1
インシデント発生日
2022-03-02
エディタ
Sean McGregor, Khoa Lam
Applied Taxonomies
CSETv1_Annotator-1 分類法のクラス
分類法の詳細Incident Number
The number of the incident in the AI Incident Database.
176
Special Interest Intangible Harm
An assessment of whether a special interest intangible harm occurred. This assessment does not consider the context of the intangible harm, if an AI was involved, or if there is characterizable class or subgroup of harmed entities. It is also not assessing if an intangible harm occurred. It is only asking if a special interest intangible harm occurred.
no
Date of Incident Year
The year in which the incident occurred. If there are multiple harms or occurrences of the incident, list the earliest. If a precise date is unavailable, but the available sources provide a basis for estimating the year, estimate. Otherwise, leave blank.
Enter in the format of YYYY
2022
Estimated Date
“Yes” if the data was estimated. “No” otherwise.
Yes
Multiple AI Interaction
“Yes” if two or more independently operating AI systems were involved. “No” otherwise.
no
Embedded
“Yes” if the AI is embedded in a physical system. “No” if it is not. “Maybe” if it is unclear.
yes
CSETv1_Annotator-3 分類法のクラス
分類法の詳細Incident Number
The number of the incident in the AI Incident Database.
176
Special Interest Intangible Harm
An assessment of whether a special interest intangible harm occurred. This assessment does not consider the context of the intangible harm, if an AI was involved, or if there is characterizable class or subgroup of harmed entities. It is also not assessing if an intangible harm occurred. It is only asking if a special interest intangible harm occurred.
no
Date of Incident Year
The year in which the incident occurred. If there are multiple harms or occurrences of the incident, list the earliest. If a precise date is unavailable, but the available sources provide a basis for estimating the year, estimate. Otherwise, leave blank.
Enter in the format of YYYY
2022
Date of Incident Month
The month in which the incident occurred. If there are multiple harms or occurrences of the incident, list the earliest. If a precise date is unavailable, but the available sources provide a basis for estimating the month, estimate. Otherwise, leave blank.
Enter in the format of MM
03
Estimated Date
“Yes” if the data was estimated. “No” otherwise.
Yes
Multiple AI Interaction
“Yes” if two or more independently operating AI systems were involved. “No” otherwise.
no
インシデントレポート
レポートタイムライン
autoblog.com · 2022
- 情報源として元のレポートを表示
- インターネットアーカイブでレポートを表示
Starting to slip into the Friday afternoon doldrums? Here's one from the let's-see-what's-on-social-media-today file: an autonomous food delivery robot putting up a noble defense against a freight locomotive after apparently becoming strand…
バリアント
「バリアント」は既存のAIインシデントと同じ原因要素を共 有し、同様な被害を引き起こし、同じ知的システムを含んだインシデントです。バリアントは完全に独立したインシデントとしてインデックスするのではなく、データベースに最初に投稿された同様なインシデントの元にインシデントのバリエーションとして一覧します。インシデントデータベースの他の投稿タイプとは違い、バリアントではインシデントデータベース以外の根拠のレポートは要求されません。詳細についてはこの研究論文を参照してください
よく似たインシデント
Did our AI mess up? Flag the unrelated incidents
よく似たインシデント
Did our AI mess up? Flag the unrelated incidents