This page shows the pre-commit working store (the raw extraction under review). This case was committed to OntServe on 2026-07-14 17:57; the committed record differs by design (deduplication, typing, and agent binding are applied at commit). View the committed record
Overview
Provenance Draft

PASS 3: Temporal Dynamics

Case 165: Public Health, Safety, and Welfare—Driverless/Autonomous Vehicle

23 entities 5 actions 5 events 7 causal chains 5 temporal relations
Timeline Overview
Action Event 10 sequenced markers
Consultant Team Assignment Beginning of the case timeline, before team deliberations
Further Study Proposal Prospective, before the autonomous vehicle operating system is utilized, if deemed necessary
Risk Team Participation During the risk assessment team deliberations, ongoing and prospective
Safety Concern Expression During the team's deliberations, prospective
Technical Options Exploration During the risk assessment process, prospective
Unavoidable Crash Hypothetical future scenario considered during risk assessment
System Outcome Selection Hypothetical future scenario, immediately upon detection of an unavoidable crash
Pedestrian Fatality Hypothetical future scenario, following the system's crash response selection
New Technology Uncertainty Preceding and during the manufacturer's consideration of the autonomous vehicle system
OWL-Time Temporal Structure 5 relations time: = w3.org/2006/time
further study proposed by Engineer A time:intervalBefore utilization/deployment of the autonomous vehicle operating system
engineering risk assessment team's recommendation time:intervalBefore operation of driverless/autonomous vehicles (potential crash scenarios)
Engineer A expressing safety concerns and exploring technical options time:intervalDuring Engineer A's participation on the engineering risk management team
manufacturer's consideration of developing the autonomous system time:intervalBefore deployment/utilization of the autonomous vehicle operating system
Engineer A's risk assessment team assignment time:intervalDuring Engineer A's consulting engagement with the automobile manufacturer
Extracted Actions (5)
Volitional professional decisions with intentions and ethical context

Description: The automobile manufacturer assigns Engineer A, a consulting professional engineer, to an engineering risk assessment team tasked with making recommendations about crash scenarios for the proposed autonomous vehicle operating system.

Temporal Marker: Beginning of the case timeline, before team deliberations instant

Fluent Transitions:
Initiates (1)
  • Engineer A Risk Assessment Team Membership

Mental State: deliberate

Intended Outcome: Obtain professional risk assessment recommendations on the autonomous vehicle operating system

Required Capabilities:
Engineering risk assessment
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • requiresCapability: Engineering risk assessment
  • initiates: Engineer A Risk Assessment Team Membership
Literal extractions (kept for synthesis)
  • description content: The automobile manufacturer assigns Engineer A, a consulting professional engineer, to an engineering risk assessment team tasked with making recommendations about crash scenarios for the proposed autonomous vehicle operating system.
  • hasAgent content: Automobile manufacturer
  • temporalMarker content: Beginning of the case timeline, before team deliberations
  • eventRoleContext content: client
  • hasMentalState content: deliberate
  • intendedOutcome content: Obtain professional risk assessment recommendations on the autonomous vehicle operating system
  • textReferences content: Engineer A is assigned to an engineering risk assessment team whose members are being asked to make a recommendation relating to potential situations that could arise in connection with the operation of driverless/autonomous vehicles
  • temporalExtent content: instant
  • temporalSequence content: 2
  • withinCompetence assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/165#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/ontology/case/165#Action_Consultant_Team_Assignment",
  "@type": "proeth:Action",
  "generatedAtTime": "2026-07-14T10:32:28.458974+00:00",
  "proeth:description": "The automobile manufacturer assigns Engineer A, a consulting professional engineer, to an engineering risk assessment team tasked with making recommendations about crash scenarios for the proposed autonomous vehicle operating system.",
  "proeth:discoveredInSection": "facts",
  "proeth:eventRoleContext": "client",
  "proeth:hasAgent": "Automobile manufacturer",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "Engineer A Risk Assessment Team Membership"
  ],
  "proeth:intendedOutcome": "Obtain professional risk assessment recommendations on the autonomous vehicle operating system",
  "proeth:requiresCapability": [
    "Engineering risk assessment"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "Beginning of the case timeline, before team deliberations",
  "proeth:temporalSequence": 2,
  "proeth:textReferences": [
    "Engineer A is assigned to an engineering risk assessment team whose members are being asked to make a recommendation relating to potential situations that could arise in connection with the operation of driverless/autonomous vehicles"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Consultant Team Assignment"
}

Description: Engineer A fully and actively participates as a member of the engineering risk management team evaluating crash-scenario behavior of the proposed autonomous vehicle operating system. The discussion presents this as Engineer A's prescribed conduct.

Temporal Marker: During the risk assessment team deliberations, ongoing and prospective interval

Fluent Transitions:
Initiates (1)
  • Active Risk Assessment Deliberation

Mental State: deliberate

Intended Outcome: Contribute professional judgment to the team's recommendation on crash-scenario behavior

Obligation Engagement:
Fulfills (1)
  • Responsibility to Fully and Actively Participate on the Risk Assessment Team
Guided By Principles:
  • Hold Paramount the Safety, Health, and Welfare of the Public
Required Capabilities:
Engineering risk assessment Professional judgment
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • fulfillsObligation: Responsibility to Fully and Actively Participate on the Risk Assessment Team
  • guidedByPrinciple: Hold Paramount the Safety, Health, and Welfare of the Public
  • requiresCapability: Engineering risk assessment; Professional judgment
  • initiates: Active Risk Assessment Deliberation
Literal extractions (kept for synthesis)
  • description content: Engineer A fully and actively participates as a member of the engineering risk management team evaluating crash-scenario behavior of the proposed autonomous vehicle operating system. The discussion presents this as Engineer A's prescribed conduct.
  • hasAgent content: Engineer A
  • temporalMarker content: During the risk assessment team deliberations, ongoing and prospective
  • eventRoleContext content: Professional Engineer, Consultant
  • hasMentalState content: deliberate
  • intendedOutcome content: Contribute professional judgment to the team's recommendation on crash-scenario behavior
  • textReferences content: Engineer A has a responsibility to fully and actively participate as a member of the engineering risk management team
  • temporalExtent content: interval
  • temporalSequence content: 3
  • withinCompetence assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/165#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/ontology/case/165#Action_Risk_Team_Participation",
  "@type": "proeth:Action",
  "generatedAtTime": "2026-07-14T10:32:28.459232+00:00",
  "proeth:description": "Engineer A fully and actively participates as a member of the engineering risk management team evaluating crash-scenario behavior of the proposed autonomous vehicle operating system. The discussion presents this as Engineer A\u0027s prescribed conduct.",
  "proeth:discoveredInSection": "discussion",
  "proeth:eventRoleContext": "Professional Engineer, Consultant",
  "proeth:fulfillsObligation": [
    "Responsibility to Fully and Actively Participate on the Risk Assessment Team"
  ],
  "proeth:guidedByPrinciple": [
    "Hold Paramount the Safety, Health, and Welfare of the Public"
  ],
  "proeth:hasAgent": "Engineer A",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "Active Risk Assessment Deliberation"
  ],
  "proeth:intendedOutcome": "Contribute professional judgment to the team\u0027s recommendation on crash-scenario behavior",
  "proeth:raisesObligation": [],
  "proeth:requiresCapability": [
    "Engineering risk assessment",
    "Professional judgment"
  ],
  "proeth:temporalExtent": "interval",
  "proeth:temporalMarker": "During the risk assessment team deliberations, ongoing and prospective",
  "proeth:temporalSequence": 3,
  "proeth:textReferences": [
    "Engineer A has a responsibility to fully and actively participate as a member of the engineering risk management team"
  ],
  "proeth:violatesObligation": [],
  "proeth:withinCompetence": true,
  "rdfs:label": "Risk Team Participation"
}

Description: Engineer A clearly and unambiguously expresses any and all concerns he has regarding the safety of the proposed autonomous vehicle operating system to the risk assessment team. This is the discussion's prescribed conduct for Engineer A.

Temporal Marker: During the team's deliberations, prospective instant

Fluent Transitions:
Initiates (1)
  • Safety Concerns Disclosed

Mental State: deliberate

Intended Outcome: Ensure safety concerns about the autonomous vehicle operating system are known to the team and the company

Obligation Engagement:
Fulfills (1)
  • Responsibility to Clearly Express Safety Concerns
Guided By Principles:
  • Hold Paramount the Safety, Health, and Welfare of the Public
  • Do No Harm
Required Capabilities:
Safety evaluation Professional communication
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • fulfillsObligation: Responsibility to Clearly Express Safety Concerns
  • guidedByPrinciple: Hold Paramount the Safety, Health, and Welfare of the Public; Do No Harm
  • requiresCapability: Safety evaluation; Professional communication
  • initiates: Safety Concerns Disclosed
Literal extractions (kept for synthesis)
  • description content: Engineer A clearly and unambiguously expresses any and all concerns he has regarding the safety of the proposed autonomous vehicle operating system to the risk assessment team. This is the discussion's prescribed conduct for Engineer A.
  • hasAgent content: Engineer A
  • temporalMarker content: During the team's deliberations, prospective
  • eventRoleContext content: Professional Engineer, Consultant
  • hasMentalState content: deliberate
  • intendedOutcome content: Ensure safety concerns about the autonomous vehicle operating system are known to the team and the company
  • textReferences content: clearly and unambiguously express any and all concerns he has regarding the safety of the proposed autonomous vehicle operation system
  • temporalExtent content: instant
  • temporalSequence content: 4
  • withinCompetence assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/165#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/ontology/case/165#Action_Safety_Concern_Expression",
  "@type": "proeth:Action",
  "generatedAtTime": "2026-07-14T10:32:28.459301+00:00",
  "proeth:description": "Engineer A clearly and unambiguously expresses any and all concerns he has regarding the safety of the proposed autonomous vehicle operating system to the risk assessment team. This is the discussion\u0027s prescribed conduct for Engineer A.",
  "proeth:discoveredInSection": "discussion",
  "proeth:eventRoleContext": "Professional Engineer, Consultant",
  "proeth:fulfillsObligation": [
    "Responsibility to Clearly Express Safety Concerns"
  ],
  "proeth:guidedByPrinciple": [
    "Hold Paramount the Safety, Health, and Welfare of the Public",
    "Do No Harm"
  ],
  "proeth:hasAgent": "Engineer A",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "Safety Concerns Disclosed"
  ],
  "proeth:intendedOutcome": "Ensure safety concerns about the autonomous vehicle operating system are known to the team and the company",
  "proeth:raisesObligation": [],
  "proeth:requiresCapability": [
    "Safety evaluation",
    "Professional communication"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "During the team\u0027s deliberations, prospective",
  "proeth:temporalSequence": 4,
  "proeth:textReferences": [
    "clearly and unambiguously express any and all concerns he has regarding the safety of the proposed autonomous vehicle operation system"
  ],
  "proeth:violatesObligation": [],
  "proeth:withinCompetence": true,
  "rdfs:label": "Safety Concern Expression"
}

Description: Engineer A explores additional potential technical options that could mitigate the risks identified in the proposed autonomous vehicle operating system, as prescribed by the discussion.

Temporal Marker: During the risk assessment process, prospective interval

Fluent Transitions:
Initiates (1)
  • Risk Mitigation Alternatives Under Consideration

Mental State: deliberate

Intended Outcome: Identify technical alternatives that mitigate the identified risks of the autonomous vehicle operating system

Obligation Engagement:
Fulfills (1)
  • Responsibility to Explore Risk-Mitigating Technical Options
Guided By Principles:
  • Do No Harm
  • Hold Paramount the Safety, Health, and Welfare of the Public
Required Capabilities:
Engineering risk assessment Technical analysis
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • fulfillsObligation: Responsibility to Explore Risk-Mitigating Technical Options
  • guidedByPrinciple: Do No Harm; Hold Paramount the Safety, Health, and Welfare of the Public
  • requiresCapability: Engineering risk assessment; Technical analysis
  • initiates: Risk Mitigation Alternatives Under Consideration
Literal extractions (kept for synthesis)
  • description content: Engineer A explores additional potential technical options that could mitigate the risks identified in the proposed autonomous vehicle operating system, as prescribed by the discussion.
  • hasAgent content: Engineer A
  • temporalMarker content: During the risk assessment process, prospective
  • eventRoleContext content: Professional Engineer, Consultant
  • hasMentalState content: deliberate
  • intendedOutcome content: Identify technical alternatives that mitigate the identified risks of the autonomous vehicle operating system
  • textReferences content: explore additional potential technical options that could mitigate the risks identified in the proposed autonomous vehicle operating system
  • temporalExtent content: interval
  • temporalSequence content: 5
  • withinCompetence assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/165#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/ontology/case/165#Action_Technical_Options_Exploration",
  "@type": "proeth:Action",
  "generatedAtTime": "2026-07-14T10:32:28.459337+00:00",
  "proeth:description": "Engineer A explores additional potential technical options that could mitigate the risks identified in the proposed autonomous vehicle operating system, as prescribed by the discussion.",
  "proeth:discoveredInSection": "discussion",
  "proeth:eventRoleContext": "Professional Engineer, Consultant",
  "proeth:fulfillsObligation": [
    "Responsibility to Explore Risk-Mitigating Technical Options"
  ],
  "proeth:guidedByPrinciple": [
    "Do No Harm",
    "Hold Paramount the Safety, Health, and Welfare of the Public"
  ],
  "proeth:hasAgent": "Engineer A",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "Risk Mitigation Alternatives Under Consideration"
  ],
  "proeth:intendedOutcome": "Identify technical alternatives that mitigate the identified risks of the autonomous vehicle operating system",
  "proeth:raisesObligation": [],
  "proeth:requiresCapability": [
    "Engineering risk assessment",
    "Technical analysis"
  ],
  "proeth:temporalExtent": "interval",
  "proeth:temporalMarker": "During the risk assessment process, prospective",
  "proeth:temporalSequence": 5,
  "proeth:textReferences": [
    "explore additional potential technical options that could mitigate the risks identified in the proposed autonomous vehicle operating system"
  ],
  "proeth:violatesObligation": [],
  "proeth:withinCompetence": true,
  "rdfs:label": "Technical Options Exploration"
}

Description: If necessary, Engineer A proposes that further study be undertaken by the company before the autonomous vehicle operating system is utilized. The discussion frames this as a conditional prospective action, to be taken if needed to fulfill the obligation to do no harm.

Temporal Marker: Prospective, before the autonomous vehicle operating system is utilized, if deemed necessary instant

Fluent Transitions:
Initiates (1)
  • Further Study Recommended Before System Utilization

Mental State: deliberate

Intended Outcome: Ensure the company undertakes additional study before deploying the autonomous vehicle operating system so that risks are adequately addressed

Foreseen Unintended Effects:

  • Delay in utilization of the autonomous vehicle operating system
Obligation Engagement:
Fulfills (1)
  • Responsibility to Propose Further Study if Necessary
Guided By Principles:
  • Do No Harm
  • Hold Paramount the Safety, Health, and Welfare of the Public
Required Capabilities:
Engineering judgment Risk assessment
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • fulfillsObligation: Responsibility to Propose Further Study if Necessary
  • guidedByPrinciple: Do No Harm; Hold Paramount the Safety, Health, and Welfare of the Public
  • requiresCapability: Engineering judgment; Risk assessment
  • initiates: Further Study Recommended Before System Utilization
Literal extractions (kept for synthesis)
  • description content: If necessary, Engineer A proposes that further study be undertaken by the company before the autonomous vehicle operating system is utilized. The discussion frames this as a conditional prospective action, to be taken if needed to fulfill the obligation to do no harm.
  • hasAgent content: Engineer A
  • temporalMarker content: Prospective, before the autonomous vehicle operating system is utilized, if deemed necessary
  • eventRoleContext content: Professional Engineer, Consultant
  • hasMentalState content: deliberate
  • intendedOutcome content: Ensure the company undertakes additional study before deploying the autonomous vehicle operating system so that risks are adequately addressed
  • foreseenUnintendedEffects content: Delay in utilization of the autonomous vehicle operating system
  • textReferences content: if necessary, Engineer A should propose that further study be undertaken by the company before the autonomous vehicle operating system is utilized
  • temporalExtent content: instant
  • temporalSequence content: 6
  • withinCompetence assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/165#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/ontology/case/165#Action_Further_Study_Proposal",
  "@type": "proeth:Action",
  "generatedAtTime": "2026-07-14T10:32:28.459364+00:00",
  "proeth:description": "If necessary, Engineer A proposes that further study be undertaken by the company before the autonomous vehicle operating system is utilized. The discussion frames this as a conditional prospective action, to be taken if needed to fulfill the obligation to do no harm.",
  "proeth:discoveredInSection": "discussion",
  "proeth:eventRoleContext": "Professional Engineer, Consultant",
  "proeth:foreseenUnintendedEffects": [
    "Delay in utilization of the autonomous vehicle operating system"
  ],
  "proeth:fulfillsObligation": [
    "Responsibility to Propose Further Study if Necessary"
  ],
  "proeth:guidedByPrinciple": [
    "Do No Harm",
    "Hold Paramount the Safety, Health, and Welfare of the Public"
  ],
  "proeth:hasAgent": "Engineer A",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "Further Study Recommended Before System Utilization"
  ],
  "proeth:intendedOutcome": "Ensure the company undertakes additional study before deploying the autonomous vehicle operating system so that risks are adequately addressed",
  "proeth:raisesObligation": [],
  "proeth:requiresCapability": [
    "Engineering judgment",
    "Risk assessment"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "Prospective, before the autonomous vehicle operating system is utilized, if deemed necessary",
  "proeth:temporalSequence": 6,
  "proeth:textReferences": [
    "if necessary, Engineer A should propose that further study be undertaken by the company before the autonomous vehicle operating system is utilized"
  ],
  "proeth:violatesObligation": [],
  "proeth:withinCompetence": true,
  "rdfs:label": "Further Study Proposal"
}
Extracted Events (5)
Occurrences that trigger ethical considerations and state changes

Description: The emergence of driverless/autonomous vehicle operating system technology introduces new uncertainties and potentially significant risk into the case, creating the conditions the risk assessment team must address.

Temporal Marker: Preceding and during the manufacturer's consideration of the autonomous vehicle system interval

Fluent Transitions:
Initiates (2)
  • Public Safety Risk
  • Risk Uncertainty State
Field classification (triples vs literals)
Relations (structural triples)
  • initiates: Public Safety Risk; Risk Uncertainty State
Literal extractions (kept for synthesis)
  • description content: The emergence of driverless/autonomous vehicle operating system technology introduces new uncertainties and potentially significant risk into the case, creating the conditions the risk assessment team must address.
  • temporalMarker content: Preceding and during the manufacturer's consideration of the autonomous vehicle system
  • textReferences content: New technologies often introduce new uncertainties and sometimes significant risk.
  • eventType content: exogenous
  • temporalExtent content: interval
  • temporalSequence content: 1
  • confidence assessment: 0.72
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/165#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/ontology/case/165#Event_New_Technology_Uncertainty",
  "@type": "proeth:Event",
  "generatedAtTime": "2026-07-14T10:32:28.460387+00:00",
  "proeth:confidence": "0.72",
  "proeth:description": "The emergence of driverless/autonomous vehicle operating system technology introduces new uncertainties and potentially significant risk into the case, creating the conditions the risk assessment team must address.",
  "proeth:discoveredInSection": "discussion",
  "proeth:eventType": "exogenous",
  "proeth:initiates": [
    "Public Safety Risk",
    "Risk Uncertainty State"
  ],
  "proeth:temporalExtent": "interval",
  "proeth:temporalMarker": "Preceding and during the manufacturer\u0027s consideration of the autonomous vehicle system",
  "proeth:temporalSequence": 1,
  "proeth:textReferences": [
    "New technologies often introduce new uncertainties and sometimes significant risk."
  ],
  "rdfs:label": "New Technology Uncertainty"
}

Description: Hypothetical scenario under consideration by the risk assessment team in which a driverless/autonomous vehicle encounters a crash situation that cannot be avoided, triggering the software's programmed response.

Temporal Marker: Hypothetical future scenario considered during risk assessment instant

Fluent Transitions:
Initiates (2)
  • Unavoidable Crash Situation
  • Public Safety Risk
Field classification (triples vs literals)
Relations (structural triples)
  • initiates: Unavoidable Crash Situation; Public Safety Risk
Literal extractions (kept for synthesis)
  • description content: Hypothetical scenario under consideration by the risk assessment team in which a driverless/autonomous vehicle encounters a crash situation that cannot be avoided, triggering the software's programmed response.
  • temporalMarker content: Hypothetical future scenario considered during risk assessment
  • textReferences content: In the event of an unavoidable crash
  • eventType content: exogenous
  • temporalExtent content: instant
  • temporalSequence content: 7
  • confidence assessment: 0.85
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/165#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/ontology/case/165#Event_Unavoidable_Crash",
  "@type": "proeth:Event",
  "generatedAtTime": "2026-07-14T10:32:28.460254+00:00",
  "proeth:confidence": "0.85",
  "proeth:description": "Hypothetical scenario under consideration by the risk assessment team in which a driverless/autonomous vehicle encounters a crash situation that cannot be avoided, triggering the software\u0027s programmed response.",
  "proeth:discoveredInSection": "facts",
  "proeth:eventType": "exogenous",
  "proeth:initiates": [
    "Unavoidable Crash Situation",
    "Public Safety Risk"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "Hypothetical future scenario considered during risk assessment",
  "proeth:temporalSequence": 7,
  "proeth:textReferences": [
    "In the event of an unavoidable crash"
  ],
  "rdfs:label": "Unavoidable Crash"
}

Description: Hypothetical automatic response in which the autonomous vehicle's software system selects a crash outcome, either the option maximizing passenger safety or the option minimizing overall harm to all parties involved.

Temporal Marker: Hypothetical future scenario, immediately upon detection of an unavoidable crash instant

Fluent Transitions:
Initiates (1)
  • Harm Allocation Determined
Field classification (triples vs literals)
Relations (structural triples)
  • initiates: Harm Allocation Determined
Literal extractions (kept for synthesis)
  • description content: Hypothetical automatic response in which the autonomous vehicle's software system selects a crash outcome, either the option maximizing passenger safety or the option minimizing overall harm to all parties involved.
  • temporalMarker content: Hypothetical future scenario, immediately upon detection of an unavoidable crash
  • textReferences content: does the vehicle’s system choose the outcome that will likely result in the greatest potential for safety for the vehicle’s passengers or does the vehicle’s software system instead choose an option in which the least amount of potential harm is done to any of those involved in an accident
  • eventType content: automatic
  • temporalExtent content: instant
  • temporalSequence content: 8
  • confidence assessment: 0.82
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/165#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/ontology/case/165#Event_System_Outcome_Selection",
  "@type": "proeth:Event",
  "generatedAtTime": "2026-07-14T10:32:28.460315+00:00",
  "proeth:confidence": "0.82",
  "proeth:description": "Hypothetical automatic response in which the autonomous vehicle\u0027s software system selects a crash outcome, either the option maximizing passenger safety or the option minimizing overall harm to all parties involved.",
  "proeth:discoveredInSection": "facts",
  "proeth:eventType": "automatic",
  "proeth:initiates": [
    "Harm Allocation Determined"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "Hypothetical future scenario, immediately upon detection of an unavoidable crash",
  "proeth:temporalSequence": 8,
  "proeth:textReferences": [
    "does the vehicle\u2019s system choose the outcome that will likely result in the greatest potential for safety for the vehicle\u2019s passengers or does the vehicle\u2019s software system instead choose an option in which the least amount of potential harm is done to any of those involved in an accident"
  ],
  "rdfs:label": "System Outcome Selection"
}

Description: Hypothetical harm outcome in which the vehicle crashes into a stationary object under the system's minimized-harm option, probably causing serious but non-life-threatening injuries to some passengers.

Temporal Marker: Hypothetical future scenario, following the system's crash response selection instant

Fluent Transitions:
Initiates (1)
  • Passenger Harm State
Field classification (triples vs literals)
Relations (structural triples)
  • initiates: Passenger Harm State
Literal extractions (kept for synthesis)
  • description content: Hypothetical harm outcome in which the vehicle crashes into a stationary object under the system's minimized-harm option, probably causing serious but non-life-threatening injuries to some passengers.
  • temporalMarker content: Hypothetical future scenario, following the system's crash response selection
  • textReferences content: having the car crash into a stationary object (e.g., telephone pole, etc.) with the probability of causing some passengers serious but non-life-threatening injuries
  • eventType content: automatic
  • temporalExtent content: instant
  • temporalSequence content: 9
  • confidence assessment: 0.8
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/165#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/ontology/case/165#Event_Passenger_Injury",
  "@type": "proeth:Event",
  "generatedAtTime": "2026-07-14T10:32:28.460343+00:00",
  "proeth:confidence": "0.8",
  "proeth:description": "Hypothetical harm outcome in which the vehicle crashes into a stationary object under the system\u0027s minimized-harm option, probably causing serious but non-life-threatening injuries to some passengers.",
  "proeth:discoveredInSection": "facts",
  "proeth:eventType": "automatic",
  "proeth:initiates": [
    "Passenger Harm State"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "Hypothetical future scenario, following the system\u0027s crash response selection",
  "proeth:temporalSequence": 9,
  "proeth:textReferences": [
    "having the car crash into a stationary object (e.g., telephone pole, etc.) with the probability of causing some passengers serious but non-life-threatening injuries"
  ],
  "rdfs:label": "Passenger Injury"
}

Description: Hypothetical harm outcome in which the vehicle strikes a pedestrian, cyclist, or motorcycle rider under the passenger-priority option, potentially causing a fatal injury.

Temporal Marker: Hypothetical future scenario, following the system's crash response selection instant

Fluent Transitions:
Initiates (1)
  • Third Party Harm State
Field classification (triples vs literals)
Relations (structural triples)
  • initiates: Third Party Harm State
Literal extractions (kept for synthesis)
  • description content: Hypothetical harm outcome in which the vehicle strikes a pedestrian, cyclist, or motorcycle rider under the passenger-priority option, potentially causing a fatal injury.
  • temporalMarker content: Hypothetical future scenario, following the system's crash response selection
  • textReferences content: striking and potentially causing a fatal injury to a pedestrian, cyclist, or motorcycle rider
  • eventType content: automatic
  • temporalExtent content: instant
  • temporalSequence content: 10
  • confidence assessment: 0.8
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/165#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/ontology/case/165#Event_Pedestrian_Fatality",
  "@type": "proeth:Event",
  "generatedAtTime": "2026-07-14T10:32:28.460366+00:00",
  "proeth:confidence": "0.8",
  "proeth:description": "Hypothetical harm outcome in which the vehicle strikes a pedestrian, cyclist, or motorcycle rider under the passenger-priority option, potentially causing a fatal injury.",
  "proeth:discoveredInSection": "facts",
  "proeth:eventType": "automatic",
  "proeth:initiates": [
    "Third Party Harm State"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "Hypothetical future scenario, following the system\u0027s crash response selection",
  "proeth:temporalSequence": 10,
  "proeth:textReferences": [
    "striking and potentially causing a fatal injury to a pedestrian, cyclist, or motorcycle rider"
  ],
  "rdfs:label": "Pedestrian Fatality"
}
Causal Chains (7)
NESS test analysis: Necessary Element of Sufficient Set

Causal Language: New technologies often introduce new uncertainties and sometimes significant risk.

Necessary Factors (NESS):
  • Manufacturer's consideration of developing a driverless/autonomous vehicle operating system
  • Recognition that the new technology introduces uncertainties and significant risk
  • Availability of Engineer A as a professional engineering consultant
Sufficient Factors:
  • Combination of novel autonomous vehicle technology + recognized safety uncertainties + corporate decision to conduct a risk assessment
Counterfactual Test: Without the emergence of uncertain autonomous vehicle technology, the manufacturer would have had no need to form a risk assessment team or assign Engineer A to it
Responsibility Attribution:

Agent: Automobile Manufacturer
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. New Technology Uncertainty
    Driverless/autonomous vehicle operating system technology emerges, introducing new uncertainties and significant risk
  2. Manufacturer Development Consideration
    Automobile manufacturer considers developing the autonomous vehicle operating system
  3. Risk Assessment Team Formation
    Manufacturer forms an engineering risk assessment team to make recommendations on potential operational situations
  4. Consultant Team Assignment
    Engineer A is assigned to the engineering risk assessment team
Field classification (triples vs literals)
Relations (structural triples)
  • cause: New Technology Uncertainty
  • effect: Consultant Team Assignment
  • responsibleAgent: Automobile Manufacturer
Literal extractions (kept for synthesis)
  • causalLanguage content: New technologies often introduce new uncertainties and sometimes significant risk.
  • necessaryFactors content: Manufacturer's consideration of developing a driverless/autonomous vehicle operating system; Recognition that the new technology introduces uncertainties and significant risk; Availability of Engineer A as a professional engineering consultant
  • sufficientFactors content: Combination of novel autonomous vehicle technology + recognized safety uncertainties + corporate decision to conduct a risk assessment
  • counterfactual content: Without the emergence of uncertain autonomous vehicle technology, the manufacturer would have had no need to form a risk assessment team or assign Engineer A to it
  • agentKnowledge content: Knew it was considering development of a driverless/autonomous vehicle operating system with potential crash scenarios requiring ethical and technical evaluation
  • interveningFactors content: Industry-wide emergence of autonomous vehicle technology; Absence of settled standards for autonomous crash-decision algorithms
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'New Technology Uncertainty', 'proeth:description': 'Driverless/autonomous vehicle operating system technology emerges, introducing new uncertainties and significant risk'}; {'proeth:step': 2, 'proeth:element': 'Manufacturer Development Consideration', 'proeth:description': 'Automobile manufacturer considers developing the autonomous vehicle operating system'}; {'proeth:step': 3, 'proeth:element': 'Risk Assessment Team Formation', 'proeth:description': 'Manufacturer forms an engineering risk assessment team to make recommendations on potential operational situations'}; {'proeth:step': 4, 'proeth:element': 'Consultant Team Assignment', 'proeth:description': 'Engineer A is assigned to the engineering risk assessment team'}
  • responsibilityType assessment: direct
  • withinAgentControl assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/165#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/ontology/case/165#CausalChain_1",
  "@type": "proeth:CausalChain",
  "generatedAtTime": "2026-07-14T10:32:28.460454+00:00",
  "proeth:agentKnowledge": "Knew it was considering development of a driverless/autonomous vehicle operating system with potential crash scenarios requiring ethical and technical evaluation",
  "proeth:causalLanguage": "New technologies often introduce new uncertainties and sometimes significant risk.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Driverless/autonomous vehicle operating system technology emerges, introducing new uncertainties and significant risk",
      "proeth:element": "New Technology Uncertainty",
      "proeth:step": 1
    },
    {
      "proeth:description": "Automobile manufacturer considers developing the autonomous vehicle operating system",
      "proeth:element": "Manufacturer Development Consideration",
      "proeth:step": 2
    },
    {
      "proeth:description": "Manufacturer forms an engineering risk assessment team to make recommendations on potential operational situations",
      "proeth:element": "Risk Assessment Team Formation",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A is assigned to the engineering risk assessment team",
      "proeth:element": "Consultant Team Assignment",
      "proeth:step": 4
    }
  ],
  "proeth:cause": "New Technology Uncertainty",
  "proeth:counterfactual": "Without the emergence of uncertain autonomous vehicle technology, the manufacturer would have had no need to form a risk assessment team or assign Engineer A to it",
  "proeth:discoveredInSection": "discussion",
  "proeth:effect": "Consultant Team Assignment",
  "proeth:interveningFactors": [
    "Industry-wide emergence of autonomous vehicle technology",
    "Absence of settled standards for autonomous crash-decision algorithms"
  ],
  "proeth:necessaryFactors": [
    "Manufacturer\u0027s consideration of developing a driverless/autonomous vehicle operating system",
    "Recognition that the new technology introduces uncertainties and significant risk",
    "Availability of Engineer A as a professional engineering consultant"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Automobile Manufacturer",
  "proeth:sufficientFactors": [
    "Combination of novel autonomous vehicle technology + recognized safety uncertainties + corporate decision to conduct a risk assessment"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Engineer A is assigned to an engineering risk assessment team whose members are being asked to make a recommendation relating to potential situations that could arise in connection with the operation of driverless/autonomous vehicles.

Necessary Factors (NESS):
  • Assignment of Engineer A to the risk assessment team
  • Engineer A's professional obligation to hold public safety paramount
  • Team mandate to evaluate crash-scenario decision-making
Sufficient Factors:
  • Assignment to the team + Engineer A's professional ethical duty to fully and actively participate
Counterfactual Test: Without assignment to the team, Engineer A would have no role in the risk evaluation and no occasion for participation
Responsibility Attribution:

Agent: Engineer A
Type: shared
Within Agent Control: Yes

Causal Sequence:
  1. Consultant Team Assignment
    Manufacturer assigns Engineer A to the engineering risk assessment team
  2. Team Mandate Definition
    Team members are asked to make recommendations on potential autonomous vehicle crash situations
  3. Risk Team Participation
    Engineer A fully and actively participates as a member of the engineering risk management team
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Consultant Team Assignment
  • effect: Risk Team Participation
  • responsibleAgent: Engineer A
Literal extractions (kept for synthesis)
  • causalLanguage content: Engineer A is assigned to an engineering risk assessment team whose members are being asked to make a recommendation relating to potential situations that could arise in connection with the operation of driverless/autonomous vehicles.
  • necessaryFactors content: Assignment of Engineer A to the risk assessment team; Engineer A's professional obligation to hold public safety paramount; Team mandate to evaluate crash-scenario decision-making
  • sufficientFactors content: Assignment to the team + Engineer A's professional ethical duty to fully and actively participate
  • counterfactual content: Without assignment to the team, Engineer A would have no role in the risk evaluation and no occasion for participation
  • agentKnowledge content: Knew the team was tasked with evaluating unavoidable crash scenarios pitting passenger safety against harm to pedestrians, cyclists, or motorcyclists
  • interveningFactors content: Corporate team structure and mandate set by the manufacturer
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Consultant Team Assignment', 'proeth:description': 'Manufacturer assigns Engineer A to the engineering risk assessment team'}; {'proeth:step': 2, 'proeth:element': 'Team Mandate Definition', 'proeth:description': 'Team members are asked to make recommendations on potential autonomous vehicle crash situations'}; {'proeth:step': 3, 'proeth:element': 'Risk Team Participation', 'proeth:description': 'Engineer A fully and actively participates as a member of the engineering risk management team'}
  • responsibilityType assessment: shared
  • withinAgentControl assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/165#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/ontology/case/165#CausalChain_2",
  "@type": "proeth:CausalChain",
  "generatedAtTime": "2026-07-14T10:32:28.460485+00:00",
  "proeth:agentKnowledge": "Knew the team was tasked with evaluating unavoidable crash scenarios pitting passenger safety against harm to pedestrians, cyclists, or motorcyclists",
  "proeth:causalLanguage": "Engineer A is assigned to an engineering risk assessment team whose members are being asked to make a recommendation relating to potential situations that could arise in connection with the operation of driverless/autonomous vehicles.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Manufacturer assigns Engineer A to the engineering risk assessment team",
      "proeth:element": "Consultant Team Assignment",
      "proeth:step": 1
    },
    {
      "proeth:description": "Team members are asked to make recommendations on potential autonomous vehicle crash situations",
      "proeth:element": "Team Mandate Definition",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A fully and actively participates as a member of the engineering risk management team",
      "proeth:element": "Risk Team Participation",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Consultant Team Assignment",
  "proeth:counterfactual": "Without assignment to the team, Engineer A would have no role in the risk evaluation and no occasion for participation",
  "proeth:discoveredInSection": "facts",
  "proeth:effect": "Risk Team Participation",
  "proeth:interveningFactors": [
    "Corporate team structure and mandate set by the manufacturer"
  ],
  "proeth:necessaryFactors": [
    "Assignment of Engineer A to the risk assessment team",
    "Engineer A\u0027s professional obligation to hold public safety paramount",
    "Team mandate to evaluate crash-scenario decision-making"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Assignment to the team + Engineer A\u0027s professional ethical duty to fully and actively participate"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: In the event of an unavoidable crash, does the vehicle’s system choose the outcome that will likely result in the greatest potential for safety for the vehicle’s passengers or does the vehicle’s software system instead choose an option in which the least amount of potential harm is done to any of those involved in an accident

Necessary Factors (NESS):
  • Occurrence of an unavoidable crash situation
  • Autonomous vehicle operating under software control
  • Pre-programmed decision logic governing crash outcomes
Sufficient Factors:
  • Unavoidable crash + software system programmed to select among available crash outcomes
Counterfactual Test: Without an unavoidable crash scenario, the system would never be forced to select between harm outcomes
Responsibility Attribution:

Agent: Automobile Manufacturer (via risk assessment team's design recommendation)
Type: indirect
Within Agent Control: Yes

Causal Sequence:
  1. System Design Decision
    Risk assessment team recommends and manufacturer programs a crash-outcome selection rule
  2. Unavoidable Crash
    The autonomous vehicle encounters a crash situation that cannot be avoided
  3. System Outcome Selection
    The vehicle's software system automatically selects a crash outcome per its programming
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Unavoidable Crash
  • effect: System Outcome Selection
  • responsibleAgent: Automobile Manufacturer (via risk assessment team's design recommendation)
Literal extractions (kept for synthesis)
  • causalLanguage content: In the event of an unavoidable crash, does the vehicle’s system choose the outcome that will likely result in the greatest potential for safety for the vehicle’s passengers or does the vehicle’s software system instead choose an option in which the least amount of potential harm is done to any of those involved in an accident
  • necessaryFactors content: Occurrence of an unavoidable crash situation; Autonomous vehicle operating under software control; Pre-programmed decision logic governing crash outcomes
  • sufficientFactors content: Unavoidable crash + software system programmed to select among available crash outcomes
  • counterfactual content: Without an unavoidable crash scenario, the system would never be forced to select between harm outcomes
  • agentKnowledge content: The manufacturer and risk team know in advance that the software must be programmed with a rule for choosing crash outcomes
  • interveningFactors content: Road conditions and third-party behavior creating the unavoidable crash; Limits of sensor and prediction technology
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'System Design Decision', 'proeth:description': 'Risk assessment team recommends and manufacturer programs a crash-outcome selection rule'}; {'proeth:step': 2, 'proeth:element': 'Unavoidable Crash', 'proeth:description': 'The autonomous vehicle encounters a crash situation that cannot be avoided'}; {'proeth:step': 3, 'proeth:element': 'System Outcome Selection', 'proeth:description': "The vehicle's software system automatically selects a crash outcome per its programming"}
  • responsibilityType assessment: indirect
  • withinAgentControl assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/165#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/ontology/case/165#CausalChain_3",
  "@type": "proeth:CausalChain",
  "generatedAtTime": "2026-07-14T10:32:28.460511+00:00",
  "proeth:agentKnowledge": "The manufacturer and risk team know in advance that the software must be programmed with a rule for choosing crash outcomes",
  "proeth:causalLanguage": "In the event of an unavoidable crash, does the vehicle\u2019s system choose the outcome that will likely result in the greatest potential for safety for the vehicle\u2019s passengers or does the vehicle\u2019s software system instead choose an option in which the least amount of potential harm is done to any of those involved in an accident",
  "proeth:causalSequence": [
    {
      "proeth:description": "Risk assessment team recommends and manufacturer programs a crash-outcome selection rule",
      "proeth:element": "System Design Decision",
      "proeth:step": 1
    },
    {
      "proeth:description": "The autonomous vehicle encounters a crash situation that cannot be avoided",
      "proeth:element": "Unavoidable Crash",
      "proeth:step": 2
    },
    {
      "proeth:description": "The vehicle\u0027s software system automatically selects a crash outcome per its programming",
      "proeth:element": "System Outcome Selection",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Unavoidable Crash",
  "proeth:counterfactual": "Without an unavoidable crash scenario, the system would never be forced to select between harm outcomes",
  "proeth:discoveredInSection": "facts",
  "proeth:effect": "System Outcome Selection",
  "proeth:interveningFactors": [
    "Road conditions and third-party behavior creating the unavoidable crash",
    "Limits of sensor and prediction technology"
  ],
  "proeth:necessaryFactors": [
    "Occurrence of an unavoidable crash situation",
    "Autonomous vehicle operating under software control",
    "Pre-programmed decision logic governing crash outcomes"
  ],
  "proeth:responsibilityType": "indirect",
  "proeth:responsibleAgent": "Automobile Manufacturer (via risk assessment team\u0027s design recommendation)",
  "proeth:sufficientFactors": [
    "Unavoidable crash + software system programmed to select among available crash outcomes"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: such as having the car crash into a stationary object (e.g., telephone pole, etc.) with the probability of causing some passengers serious but non-life-threatening injuries instead of striking and potentially causing a fatal injury to a pedestrian, cyclist, or motorcycle rider

Necessary Factors (NESS):
  • Unavoidable crash situation
  • Software programmed to minimize total harm to all involved
  • Presence of a stationary object as an available crash target
Sufficient Factors:
  • Harm-minimization programming + unavoidable crash + stationary object option chosen
Counterfactual Test: If the system were instead programmed to maximize passenger safety, the vehicle would not crash into the stationary object and passengers would likely avoid serious injury
Responsibility Attribution:

Agent: Automobile Manufacturer and engineering risk assessment team
Type: shared
Within Agent Control: Yes

Causal Sequence:
  1. System Design Decision
    System programmed to choose the option with the least amount of potential harm to all involved
  2. Unavoidable Crash
    Vehicle enters an unavoidable crash situation
  3. System Outcome Selection
    Software selects crashing into a stationary object over striking a pedestrian, cyclist, or motorcycle rider
  4. Passenger Injury
    Passengers sustain serious but non-life-threatening injuries
Field classification (triples vs literals)
Relations (structural triples)
  • cause: System Outcome Selection
  • effect: Passenger Injury
  • responsibleAgent: Automobile Manufacturer and engineering risk assessment team
Literal extractions (kept for synthesis)
  • causalLanguage content: such as having the car crash into a stationary object (e.g., telephone pole, etc.) with the probability of causing some passengers serious but non-life-threatening injuries instead of striking and potentially causing a fatal injury to a pedestrian, cyclist, or motorcycle rider
  • necessaryFactors content: Unavoidable crash situation; Software programmed to minimize total harm to all involved; Presence of a stationary object as an available crash target
  • sufficientFactors content: Harm-minimization programming + unavoidable crash + stationary object option chosen
  • counterfactual content: If the system were instead programmed to maximize passenger safety, the vehicle would not crash into the stationary object and passengers would likely avoid serious injury
  • agentKnowledge content: Designers knowingly programmed the ethical trade-off with the probability of causing some passengers serious but non-life-threatening injuries
  • interveningFactors content: The unavoidable crash circumstances; Physical environment (location of the stationary object)
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'System Design Decision', 'proeth:description': 'System programmed to choose the option with the least amount of potential harm to all involved'}; {'proeth:step': 2, 'proeth:element': 'Unavoidable Crash', 'proeth:description': 'Vehicle enters an unavoidable crash situation'}; {'proeth:step': 3, 'proeth:element': 'System Outcome Selection', 'proeth:description': 'Software selects crashing into a stationary object over striking a pedestrian, cyclist, or motorcycle rider'}; {'proeth:step': 4, 'proeth:element': 'Passenger Injury', 'proeth:description': 'Passengers sustain serious but non-life-threatening injuries'}
  • responsibilityType assessment: shared
  • withinAgentControl assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/165#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/ontology/case/165#CausalChain_4",
  "@type": "proeth:CausalChain",
  "generatedAtTime": "2026-07-14T10:32:28.460533+00:00",
  "proeth:agentKnowledge": "Designers knowingly programmed the ethical trade-off with the probability of causing some passengers serious but non-life-threatening injuries",
  "proeth:causalLanguage": "such as having the car crash into a stationary object (e.g., telephone pole, etc.) with the probability of causing some passengers serious but non-life-threatening injuries instead of striking and potentially causing a fatal injury to a pedestrian, cyclist, or motorcycle rider",
  "proeth:causalSequence": [
    {
      "proeth:description": "System programmed to choose the option with the least amount of potential harm to all involved",
      "proeth:element": "System Design Decision",
      "proeth:step": 1
    },
    {
      "proeth:description": "Vehicle enters an unavoidable crash situation",
      "proeth:element": "Unavoidable Crash",
      "proeth:step": 2
    },
    {
      "proeth:description": "Software selects crashing into a stationary object over striking a pedestrian, cyclist, or motorcycle rider",
      "proeth:element": "System Outcome Selection",
      "proeth:step": 3
    },
    {
      "proeth:description": "Passengers sustain serious but non-life-threatening injuries",
      "proeth:element": "Passenger Injury",
      "proeth:step": 4
    }
  ],
  "proeth:cause": "System Outcome Selection",
  "proeth:counterfactual": "If the system were instead programmed to maximize passenger safety, the vehicle would not crash into the stationary object and passengers would likely avoid serious injury",
  "proeth:discoveredInSection": "facts",
  "proeth:effect": "Passenger Injury",
  "proeth:interveningFactors": [
    "The unavoidable crash circumstances",
    "Physical environment (location of the stationary object)"
  ],
  "proeth:necessaryFactors": [
    "Unavoidable crash situation",
    "Software programmed to minimize total harm to all involved",
    "Presence of a stationary object as an available crash target"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Automobile Manufacturer and engineering risk assessment team",
  "proeth:sufficientFactors": [
    "Harm-minimization programming + unavoidable crash + stationary object option chosen"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: does the vehicle’s system choose the outcome that will likely result in the greatest potential for safety for the vehicle’s passengers ... instead of striking and potentially causing a fatal injury to a pedestrian, cyclist, or motorcycle rider?

Necessary Factors (NESS):
  • Unavoidable crash situation
  • Software programmed to prioritize passenger safety over harm to others
  • Presence of a pedestrian, cyclist, or motorcycle rider in the crash path
Sufficient Factors:
  • Passenger-priority programming + unavoidable crash + vulnerable road user in path
Counterfactual Test: If the system were programmed to minimize total harm (crash into stationary object), the pedestrian, cyclist, or motorcyclist would likely not be fatally struck
Responsibility Attribution:

Agent: Automobile Manufacturer and engineering risk assessment team
Type: shared
Within Agent Control: Yes

Causal Sequence:
  1. System Design Decision
    System programmed to choose the outcome with the greatest potential for safety for the vehicle's passengers
  2. Unavoidable Crash
    Vehicle enters an unavoidable crash situation with a vulnerable road user present
  3. System Outcome Selection
    Software selects the passenger-protective option, directing the vehicle toward the pedestrian, cyclist, or motorcyclist
  4. Pedestrian Fatality
    Pedestrian, cyclist, or motorcycle rider is struck and potentially fatally injured
Field classification (triples vs literals)
Relations (structural triples)
  • cause: System Outcome Selection
  • effect: Pedestrian Fatality
  • responsibleAgent: Automobile Manufacturer and engineering risk assessment team
Literal extractions (kept for synthesis)
  • causalLanguage content: does the vehicle’s system choose the outcome that will likely result in the greatest potential for safety for the vehicle’s passengers ... instead of striking and potentially causing a fatal injury to a pedestrian, cyclist, or motorcycle rider?
  • necessaryFactors content: Unavoidable crash situation; Software programmed to prioritize passenger safety over harm to others; Presence of a pedestrian, cyclist, or motorcycle rider in the crash path
  • sufficientFactors content: Passenger-priority programming + unavoidable crash + vulnerable road user in path
  • counterfactual content: If the system were programmed to minimize total harm (crash into stationary object), the pedestrian, cyclist, or motorcyclist would likely not be fatally struck
  • agentKnowledge content: Designers knowingly considered programming that could result in striking and potentially causing a fatal injury to a pedestrian, cyclist, or motorcycle rider
  • interveningFactors content: The unavoidable crash circumstances; Presence and position of vulnerable road users
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'System Design Decision', 'proeth:description': "System programmed to choose the outcome with the greatest potential for safety for the vehicle's passengers"}; {'proeth:step': 2, 'proeth:element': 'Unavoidable Crash', 'proeth:description': 'Vehicle enters an unavoidable crash situation with a vulnerable road user present'}; {'proeth:step': 3, 'proeth:element': 'System Outcome Selection', 'proeth:description': 'Software selects the passenger-protective option, directing the vehicle toward the pedestrian, cyclist, or motorcyclist'}; {'proeth:step': 4, 'proeth:element': 'Pedestrian Fatality', 'proeth:description': 'Pedestrian, cyclist, or motorcycle rider is struck and potentially fatally injured'}
  • responsibilityType assessment: shared
  • withinAgentControl assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/165#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/ontology/case/165#CausalChain_5",
  "@type": "proeth:CausalChain",
  "generatedAtTime": "2026-07-14T10:32:28.460555+00:00",
  "proeth:agentKnowledge": "Designers knowingly considered programming that could result in striking and potentially causing a fatal injury to a pedestrian, cyclist, or motorcycle rider",
  "proeth:causalLanguage": "does the vehicle\u2019s system choose the outcome that will likely result in the greatest potential for safety for the vehicle\u2019s passengers ... instead of striking and potentially causing a fatal injury to a pedestrian, cyclist, or motorcycle rider?",
  "proeth:causalSequence": [
    {
      "proeth:description": "System programmed to choose the outcome with the greatest potential for safety for the vehicle\u0027s passengers",
      "proeth:element": "System Design Decision",
      "proeth:step": 1
    },
    {
      "proeth:description": "Vehicle enters an unavoidable crash situation with a vulnerable road user present",
      "proeth:element": "Unavoidable Crash",
      "proeth:step": 2
    },
    {
      "proeth:description": "Software selects the passenger-protective option, directing the vehicle toward the pedestrian, cyclist, or motorcyclist",
      "proeth:element": "System Outcome Selection",
      "proeth:step": 3
    },
    {
      "proeth:description": "Pedestrian, cyclist, or motorcycle rider is struck and potentially fatally injured",
      "proeth:element": "Pedestrian Fatality",
      "proeth:step": 4
    }
  ],
  "proeth:cause": "System Outcome Selection",
  "proeth:counterfactual": "If the system were programmed to minimize total harm (crash into stationary object), the pedestrian, cyclist, or motorcyclist would likely not be fatally struck",
  "proeth:discoveredInSection": "facts",
  "proeth:effect": "Pedestrian Fatality",
  "proeth:interveningFactors": [
    "The unavoidable crash circumstances",
    "Presence and position of vulnerable road users"
  ],
  "proeth:necessaryFactors": [
    "Unavoidable crash situation",
    "Software programmed to prioritize passenger safety over harm to others",
    "Presence of a pedestrian, cyclist, or motorcycle rider in the crash path"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Automobile Manufacturer and engineering risk assessment team",
  "proeth:sufficientFactors": [
    "Passenger-priority programming + unavoidable crash + vulnerable road user in path"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Engineer A has a responsibility to fully and actively participate as a member of the engineering risk management team, clearly and unambiguously express any and all concerns he has regarding the safety of the proposed autonomous vehicle operation system

Necessary Factors (NESS):
  • Engineer A's active membership on the risk management team
  • Identification of safety concerns through team evaluation of crash scenarios
  • Professional duty to hold public safety paramount
Sufficient Factors:
  • Active team participation + identified safety risks + ethical obligation to communicate concerns clearly
Counterfactual Test: Without full and active participation on the team, Engineer A would lack the forum and information to express safety concerns
Responsibility Attribution:

Agent: Engineer A
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Risk Team Participation
    Engineer A fully and actively participates in evaluating the autonomous vehicle operating system
  2. Risk Identification
    Team consideration of unavoidable crash scenarios reveals safety concerns
  3. Safety Concern Expression
    Engineer A clearly and unambiguously expresses all safety concerns
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Risk Team Participation
  • effect: Safety Concern Expression
  • responsibleAgent: Engineer A
Literal extractions (kept for synthesis)
  • causalLanguage content: Engineer A has a responsibility to fully and actively participate as a member of the engineering risk management team, clearly and unambiguously express any and all concerns he has regarding the safety of the proposed autonomous vehicle operation system
  • necessaryFactors content: Engineer A's active membership on the risk management team; Identification of safety concerns through team evaluation of crash scenarios; Professional duty to hold public safety paramount
  • sufficientFactors content: Active team participation + identified safety risks + ethical obligation to communicate concerns clearly
  • counterfactual content: Without full and active participation on the team, Engineer A would lack the forum and information to express safety concerns
  • agentKnowledge content: Knew the overriding ethical responsibility of a professional engineer is to hold paramount the safety, health, and welfare of the public
  • interveningFactors content: Business considerations of the manufacturer; Team dynamics and decision-making process
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Risk Team Participation', 'proeth:description': 'Engineer A fully and actively participates in evaluating the autonomous vehicle operating system'}; {'proeth:step': 2, 'proeth:element': 'Risk Identification', 'proeth:description': 'Team consideration of unavoidable crash scenarios reveals safety concerns'}; {'proeth:step': 3, 'proeth:element': 'Safety Concern Expression', 'proeth:description': 'Engineer A clearly and unambiguously expresses all safety concerns'}
  • responsibilityType assessment: direct
  • withinAgentControl assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/165#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/ontology/case/165#CausalChain_6",
  "@type": "proeth:CausalChain",
  "generatedAtTime": "2026-07-14T10:32:28.460574+00:00",
  "proeth:agentKnowledge": "Knew the overriding ethical responsibility of a professional engineer is to hold paramount the safety, health, and welfare of the public",
  "proeth:causalLanguage": "Engineer A has a responsibility to fully and actively participate as a member of the engineering risk management team, clearly and unambiguously express any and all concerns he has regarding the safety of the proposed autonomous vehicle operation system",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A fully and actively participates in evaluating the autonomous vehicle operating system",
      "proeth:element": "Risk Team Participation",
      "proeth:step": 1
    },
    {
      "proeth:description": "Team consideration of unavoidable crash scenarios reveals safety concerns",
      "proeth:element": "Risk Identification",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A clearly and unambiguously expresses all safety concerns",
      "proeth:element": "Safety Concern Expression",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Risk Team Participation",
  "proeth:counterfactual": "Without full and active participation on the team, Engineer A would lack the forum and information to express safety concerns",
  "proeth:discoveredInSection": "discussion",
  "proeth:effect": "Safety Concern Expression",
  "proeth:interveningFactors": [
    "Business considerations of the manufacturer",
    "Team dynamics and decision-making process"
  ],
  "proeth:necessaryFactors": [
    "Engineer A\u0027s active membership on the risk management team",
    "Identification of safety concerns through team evaluation of crash scenarios",
    "Professional duty to hold public safety paramount"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Active team participation + identified safety risks + ethical obligation to communicate concerns clearly"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: In light of the fact that engineers should strive to seek to do no harm in the performance of their professional services, if necessary, Engineer A should propose that further study be undertaken by the company before the autonomous vehicle operating system is utilized.

Necessary Factors (NESS):
  • Exploration of additional technical options to mitigate identified risks
  • Determination that existing options do not adequately resolve safety concerns
  • Ethical principle that engineers should strive to do no harm
Sufficient Factors:
  • Unresolved risks after exploring technical options + duty to do no harm + Engineer A's advisory role
Counterfactual Test: If exploration of technical options had fully mitigated the identified risks, a proposal for further study would not be necessary
Responsibility Attribution:

Agent: Engineer A
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Safety Concern Expression
    Engineer A expresses concerns about the safety of the proposed autonomous vehicle operating system
  2. Technical Options Exploration
    Engineer A explores additional potential technical options that could mitigate the identified risks
  3. Risk Assessment Conclusion
    Available options are judged insufficient to resolve the safety concerns
  4. Further Study Proposal
    Engineer A proposes that further study be undertaken before the system is utilized
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Technical Options Exploration
  • effect: Further Study Proposal
  • responsibleAgent: Engineer A
Literal extractions (kept for synthesis)
  • causalLanguage content: In light of the fact that engineers should strive to seek to do no harm in the performance of their professional services, if necessary, Engineer A should propose that further study be undertaken by the company before the autonomous vehicle operating system is utilized.
  • necessaryFactors content: Exploration of additional technical options to mitigate identified risks; Determination that existing options do not adequately resolve safety concerns; Ethical principle that engineers should strive to do no harm
  • sufficientFactors content: Unresolved risks after exploring technical options + duty to do no harm + Engineer A's advisory role
  • counterfactual content: If exploration of technical options had fully mitigated the identified risks, a proposal for further study would not be necessary
  • agentKnowledge content: Knew from BER Case 96-4 precedent that recommendations should be based solely on technical findings to permit the company to make an informed decision in furtherance of public health, safety, and welfare
  • interveningFactors content: Company's business considerations; Company's ultimate authority to decide whether to undertake further study
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Safety Concern Expression', 'proeth:description': 'Engineer A expresses concerns about the safety of the proposed autonomous vehicle operating system'}; {'proeth:step': 2, 'proeth:element': 'Technical Options Exploration', 'proeth:description': 'Engineer A explores additional potential technical options that could mitigate the identified risks'}; {'proeth:step': 3, 'proeth:element': 'Risk Assessment Conclusion', 'proeth:description': 'Available options are judged insufficient to resolve the safety concerns'}; {'proeth:step': 4, 'proeth:element': 'Further Study Proposal', 'proeth:description': 'Engineer A proposes that further study be undertaken before the system is utilized'}
  • responsibilityType assessment: direct
  • withinAgentControl assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/165#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/ontology/case/165#CausalChain_7",
  "@type": "proeth:CausalChain",
  "generatedAtTime": "2026-07-14T10:32:28.460592+00:00",
  "proeth:agentKnowledge": "Knew from BER Case 96-4 precedent that recommendations should be based solely on technical findings to permit the company to make an informed decision in furtherance of public health, safety, and welfare",
  "proeth:causalLanguage": "In light of the fact that engineers should strive to seek to do no harm in the performance of their professional services, if necessary, Engineer A should propose that further study be undertaken by the company before the autonomous vehicle operating system is utilized.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A expresses concerns about the safety of the proposed autonomous vehicle operating system",
      "proeth:element": "Safety Concern Expression",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A explores additional potential technical options that could mitigate the identified risks",
      "proeth:element": "Technical Options Exploration",
      "proeth:step": 2
    },
    {
      "proeth:description": "Available options are judged insufficient to resolve the safety concerns",
      "proeth:element": "Risk Assessment Conclusion",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A proposes that further study be undertaken before the system is utilized",
      "proeth:element": "Further Study Proposal",
      "proeth:step": 4
    }
  ],
  "proeth:cause": "Technical Options Exploration",
  "proeth:counterfactual": "If exploration of technical options had fully mitigated the identified risks, a proposal for further study would not be necessary",
  "proeth:discoveredInSection": "discussion",
  "proeth:effect": "Further Study Proposal",
  "proeth:interveningFactors": [
    "Company\u0027s business considerations",
    "Company\u0027s ultimate authority to decide whether to undertake further study"
  ],
  "proeth:necessaryFactors": [
    "Exploration of additional technical options to mitigate identified risks",
    "Determination that existing options do not adequately resolve safety concerns",
    "Ethical principle that engineers should strive to do no harm"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Unresolved risks after exploring technical options + duty to do no harm + Engineer A\u0027s advisory role"
  ],
  "proeth:withinAgentControl": true
}
Allen Temporal Relations (5)
Interval algebra relationships with OWL-Time standard properties
From Entity Allen Relation To Entity OWL-Time Property Evidence
further study proposed by Engineer A before
Entity1 is before Entity2 		utilization/deployment of the autonomous vehicle operating system time:intervalBefore
http://www.w3.org/2006/time#intervalBefore 		Engineer A should propose that further study be undertaken by the company before the autonomous vehi... [more]
engineering risk assessment team's recommendation before
Entity1 is before Entity2 		operation of driverless/autonomous vehicles (potential crash scenarios) time:intervalBefore
http://www.w3.org/2006/time#intervalBefore 		assigned to an engineering risk assessment team whose members are being asked to make a recommendati... [more]
Engineer A expressing safety concerns and exploring technical options during
Entity1 occurs entirely within the duration of Entity2 		Engineer A's participation on the engineering risk management team time:intervalDuring
http://www.w3.org/2006/time#intervalDuring 		Engineer A has a responsibility to fully and actively participate as a member of the engineering ris... [more]
manufacturer's consideration of developing the autonomous system before
Entity1 is before Entity2 		deployment/utilization of the autonomous vehicle operating system time:intervalBefore
http://www.w3.org/2006/time#intervalBefore 		an automobile manufacturer that is considering the development of a driverless/autonomous vehicle op... [more]
Engineer A's risk assessment team assignment during
Entity1 occurs entirely within the duration of Entity2 		Engineer A's consulting engagement with the automobile manufacturer time:intervalDuring
http://www.w3.org/2006/time#intervalDuring 		Engineer A is a professional engineer working as a consultant to an automobile manufacturer ... Engi... [more]
About Allen Relations & OWL-Time

Allen's Interval Algebra provides 13 basic temporal relations between intervals. These relations are mapped to OWL-Time standard properties for interoperability with Semantic Web temporal reasoning systems and SPARQL queries.

Each relation includes both a ProEthica custom property and a time:* OWL-Time property for maximum compatibility.

Back to Extraction Continue to Step 4

© Licensed under the GNU GPL v3