PASS 3: Temporal Dynamics
Case 71: Failure To Include Information In Engineering Report
Timeline Overview
OWL-Time Temporal Structure 18 relations time: = w3.org/2006/time
Extracted Actions (12)
Volitional professional decisions with intentions and ethical contextDescription: Engineer A accepted retention by the municipality to design a dock supported on a foundation of 90 piles.
Temporal Marker: Before construction, at project inception interval
Fluent Transitions:
- Engineer A Client Engagement
Mental State: deliberate
Intended Outcome: Provide the municipality with a professionally designed dock foundation
Required Capabilities:
Field classification (triples vs literals)
requiresCapability: Structural and foundation design; Pile design calculationsinitiates: Engineer A Client Engagement
descriptioncontent: Engineer A accepted retention by the municipality to design a dock supported on a foundation of 90 piles.hasAgentcontent: Engineer AtemporalMarkercontent: Before construction, at project inceptioneventRoleContextcontent: Design EngineerhasMentalStatecontent: deliberateintendedOutcomecontent: Provide the municipality with a professionally designed dock foundationtextReferencescontent: Engineer A was retained by a municipality to design a dock on a supporting foundation of 90 piles.temporalExtentcontent: intervaltemporalSequencecontent: 1withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/71#",
"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/71#Action_Design_Engagement_Acceptance",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-13T07:28:03.172407+00:00",
"proeth:description": "Engineer A accepted retention by the municipality to design a dock supported on a foundation of 90 piles.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "Design Engineer",
"proeth:hasAgent": "Engineer A",
"proeth:hasMentalState": "deliberate",
"proeth:initiates": [
"Engineer A Client Engagement"
],
"proeth:intendedOutcome": "Provide the municipality with a professionally designed dock foundation",
"proeth:requiresCapability": [
"Structural and foundation design",
"Pile design calculations"
],
"proeth:temporalExtent": "interval",
"proeth:temporalMarker": "Before construction, at project inception",
"proeth:temporalSequence": 1,
"proeth:textReferences": [
"Engineer A was retained by a municipality to design a dock on a supporting foundation of 90 piles."
],
"proeth:withinCompetence": true,
"rdfs:label": "Design Engagement Acceptance"
}
Description: During the mediation, the municipality brought in expert witnesses to support its case that many piles did not initially meet driving resistance requirements.
Temporal Marker: During the mediation interval
Fluent Transitions:
- Disputed Pile Adequacy Question
Mental State: deliberate
Intended Outcome: Support the municipality's position in the settlement cost dispute
Foreseen Unintended Effects:
- Polarizing the presentation of technical facts along adversarial lines
Required Capabilities:
Field classification (triples vs literals)
requiresCapability: Litigation strategyinitiates: Disputed Pile Adequacy Question
descriptioncontent: During the mediation, the municipality brought in expert witnesses to support its case that many piles did not initially meet driving resistance requirements.hasAgentcontent: MunicipalitytemporalMarkercontent: During the mediationeventRoleContextcontent: Client and Co-defendanthasMentalStatecontent: deliberateintendedOutcomecontent: Support the municipality's position in the settlement cost disputeforeseenUnintendedEffectscontent: Polarizing the presentation of technical facts along adversarial linestextReferencescontent: During the mediation, the municipality brought in expert witnesses to support their case.temporalExtentcontent: intervaltemporalSequencecontent: 4withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/71#",
"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/71#Action_Expert_Witness_Retention",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-13T07:28:03.172574+00:00",
"proeth:description": "During the mediation, the municipality brought in expert witnesses to support its case that many piles did not initially meet driving resistance requirements.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "Client and Co-defendant",
"proeth:foreseenUnintendedEffects": [
"Polarizing the presentation of technical facts along adversarial lines"
],
"proeth:hasAgent": "Municipality",
"proeth:hasMentalState": "deliberate",
"proeth:initiates": [
"Disputed Pile Adequacy Question"
],
"proeth:intendedOutcome": "Support the municipality\u0027s position in the settlement cost dispute",
"proeth:requiresCapability": [
"Litigation strategy"
],
"proeth:temporalExtent": "interval",
"proeth:temporalMarker": "During the mediation",
"proeth:temporalSequence": 4,
"proeth:textReferences": [
"During the mediation, the municipality brought in expert witnesses to support their case."
],
"proeth:withinCompetence": true,
"rdfs:label": "Expert Witness Retention"
}
Description: Engineer A testified that the geotechnical firm's report expected the piles to gain sufficient additional strength within 30 days to meet driving resistance requirements.
Temporal Marker: During the mediation instant
Fluent Transitions:
- Pile Set Up Strength Question Framed for Testing
Mental State: deliberate
Intended Outcome: Defend the adequacy of the pile design based on the geotechnical report's set up strength prediction
Obligation Engagement:
- Include All Relevant and Pertinent Information
Guided By Principles:
- Exponents of All Available Technical Facts
Required Capabilities:
Field classification (triples vs literals)
fulfillsObligation: Include All Relevant and Pertinent InformationguidedByPrinciple: Exponents of All Available Technical FactsrequiresCapability: Geotechnical interpretation; Expert testimonyinitiates: Pile Set Up Strength Question Framed for Testing
descriptioncontent: Engineer A testified that the geotechnical firm's report expected the piles to gain sufficient additional strength within 30 days to meet driving resistance requirements.hasAgentcontent: Engineer AtemporalMarkercontent: During the mediationeventRoleContextcontent: Design EngineerhasMentalStatecontent: deliberateintendedOutcomecontent: Defend the adequacy of the pile design based on the geotechnical report's set up strength predictiontextReferencescontent: Engineer A testified that the geotechnical firm's report expected that the piles would gain sufficient additional strength within 30 days to meet driving resistance requirements.temporalExtentcontent: instanttemporalSequencecontent: 5withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/71#",
"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/71#Action_Design_Basis_Testimony",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-13T07:28:03.172603+00:00",
"proeth:description": "Engineer A testified that the geotechnical firm\u0027s report expected the piles to gain sufficient additional strength within 30 days to meet driving resistance requirements.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "Design Engineer",
"proeth:fulfillsObligation": [
"Include All Relevant and Pertinent Information"
],
"proeth:guidedByPrinciple": [
"Exponents of All Available Technical Facts"
],
"proeth:hasAgent": "Engineer A",
"proeth:hasMentalState": "deliberate",
"proeth:initiates": [
"Pile Set Up Strength Question Framed for Testing"
],
"proeth:intendedOutcome": "Defend the adequacy of the pile design based on the geotechnical report\u0027s set up strength prediction",
"proeth:raisesObligation": [],
"proeth:requiresCapability": [
"Geotechnical interpretation",
"Expert testimony"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "During the mediation",
"proeth:temporalSequence": 5,
"proeth:textReferences": [
"Engineer A testified that the geotechnical firm\u0027s report expected that the piles would gain sufficient additional strength within 30 days to meet driving resistance requirements."
],
"proeth:violatesObligation": [],
"proeth:withinCompetence": true,
"rdfs:label": "Design Basis Testimony"
}
Description: The municipality retained Engineer B to supervise the driving of several test piles to test whether the piles would gain sufficient strength to meet the design calculation requirements.
Temporal Marker: After the mediation testimony, to test Engineer A's conclusion instant
Fluent Transitions:
- Test Pile Program Engagement
Mental State: deliberate
Intended Outcome: Test the criteria and professional judgment upon which Engineer A's conclusions were based
Required Capabilities:
Field classification (triples vs literals)
requiresCapability: Engagement of qualified engineering servicesinitiates: Test Pile Program Engagement
descriptioncontent: The municipality retained Engineer B to supervise the driving of several test piles to test whether the piles would gain sufficient strength to meet the design calculation requirements.hasAgentcontent: MunicipalitytemporalMarkercontent: After the mediation testimony, to test Engineer A's conclusioneventRoleContextcontent: ClienthasMentalStatecontent: deliberateintendedOutcomecontent: Test the criteria and professional judgment upon which Engineer A's conclusions were basedtextReferencescontent: the municipality retained Engineer B to supervise the driving of several test piles to see whether the piles would gain sufficient strength to meet the design calculation requirementstemporalExtentcontent: instanttemporalSequencecontent: 6withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/71#",
"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/71#Action_Test_Supervisor_Retention",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-13T07:28:03.172628+00:00",
"proeth:description": "The municipality retained Engineer B to supervise the driving of several test piles to test whether the piles would gain sufficient strength to meet the design calculation requirements.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "Client",
"proeth:hasAgent": "Municipality",
"proeth:hasMentalState": "deliberate",
"proeth:initiates": [
"Test Pile Program Engagement"
],
"proeth:intendedOutcome": "Test the criteria and professional judgment upon which Engineer A\u0027s conclusions were based",
"proeth:requiresCapability": [
"Engagement of qualified engineering services"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "After the mediation testimony, to test Engineer A\u0027s conclusion",
"proeth:temporalSequence": 6,
"proeth:textReferences": [
"the municipality retained Engineer B to supervise the driving of several test piles to see whether the piles would gain sufficient strength to meet the design calculation requirements"
],
"proeth:withinCompetence": true,
"rdfs:label": "Test Supervisor Retention"
}
Description: Engineer A retained an independent geotechnical consultant to observe the test pile driving program.
Temporal Marker: At the start of the test pile program instant
Fluent Transitions:
- Independent Observation of Test Program
Mental State: deliberate
Intended Outcome: Obtain independent professional observation of the test conditions and results
Guided By Principles:
- Exponents of All Available Technical Facts
Required Capabilities:
Field classification (triples vs literals)
guidedByPrinciple: Exponents of All Available Technical FactsrequiresCapability: Selection of qualified geotechnical expertiseinitiates: Independent Observation of Test Program
descriptioncontent: Engineer A retained an independent geotechnical consultant to observe the test pile driving program.hasAgentcontent: Engineer AtemporalMarkercontent: At the start of the test pile programeventRoleContextcontent: Design EngineerhasMentalStatecontent: deliberateintendedOutcomecontent: Obtain independent professional observation of the test conditions and resultstextReferencescontent: An independent geotechnical consultant was retained by Engineer A to observe the test.temporalExtentcontent: instanttemporalSequencecontent: 7withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/71#",
"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/71#Action_Independent_Observer_Retention",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-13T07:28:03.172654+00:00",
"proeth:description": "Engineer A retained an independent geotechnical consultant to observe the test pile driving program.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "Design Engineer",
"proeth:guidedByPrinciple": [
"Exponents of All Available Technical Facts"
],
"proeth:hasAgent": "Engineer A",
"proeth:hasMentalState": "deliberate",
"proeth:initiates": [
"Independent Observation of Test Program"
],
"proeth:intendedOutcome": "Obtain independent professional observation of the test conditions and results",
"proeth:requiresCapability": [
"Selection of qualified geotechnical expertise"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "At the start of the test pile program",
"proeth:temporalSequence": 7,
"proeth:textReferences": [
"An independent geotechnical consultant was retained by Engineer A to observe the test."
],
"proeth:withinCompetence": true,
"rdfs:label": "Independent Observer Retention"
}
Description: Engineer B conducted the test pile program without duplicating the original driving conditions, using a vibratory hammer, driving to different penetration depths, and dropping the hammer before blow counts commenced.
Temporal Marker: During the test pile driving program interval
Fluent Transitions:
- Non-Comparable Test Conditions
Mental State: deliberate
Intended Outcome: Complete the test pile driving program to measure set up strength
Foreseen Unintended Effects:
- Compromised comparability with the original pile driving conditions
Obligation Engagement:
- Fact-Gathering Diligence
Required Capabilities:
Field classification (triples vs literals)
requiresCapability: Pile driving test supervision; Dynamic testing methodologyinitiates: Non-Comparable Test ConditionsraisesObligation: Fact-Gathering Diligence
descriptioncontent: Engineer B conducted the test pile program without duplicating the original driving conditions, using a vibratory hammer, driving to different penetration depths, and dropping the hammer before blow counts commenced.hasAgentcontent: Engineer BtemporalMarkercontent: During the test pile driving programeventRoleContextcontent: Test Program SupervisorhasMentalStatecontent: deliberateintendedOutcomecontent: Complete the test pile driving program to measure set up strengthforeseenUnintendedEffectscontent: Compromised comparability with the original pile driving conditionstextReferencescontent: Driving conditions were not duplicated in driving the test piles in that a vibratory hammer was used for the test piles and not used in the original driving.; after the 30 day set up, the driving hammer was dropped several times to start the hammer before the record of blow counts commencedtemporalExtentcontent: intervaltemporalSequencecontent: 8withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/71#",
"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/71#Action_Test_Condition_Deviation",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-13T07:28:03.172678+00:00",
"proeth:description": "Engineer B conducted the test pile program without duplicating the original driving conditions, using a vibratory hammer, driving to different penetration depths, and dropping the hammer before blow counts commenced.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "Test Program Supervisor",
"proeth:foreseenUnintendedEffects": [
"Compromised comparability with the original pile driving conditions"
],
"proeth:fulfillsObligation": [],
"proeth:hasAgent": "Engineer B",
"proeth:hasMentalState": "deliberate",
"proeth:initiates": [
"Non-Comparable Test Conditions"
],
"proeth:intendedOutcome": "Complete the test pile driving program to measure set up strength",
"proeth:raisesObligation": [
"Fact-Gathering Diligence"
],
"proeth:requiresCapability": [
"Pile driving test supervision",
"Dynamic testing methodology"
],
"proeth:temporalExtent": "interval",
"proeth:temporalMarker": "During the test pile driving program",
"proeth:temporalSequence": 8,
"proeth:textReferences": [
"Driving conditions were not duplicated in driving the test piles in that a vibratory hammer was used for the test piles and not used in the original driving.",
"after the 30 day set up, the driving hammer was dropped several times to start the hammer before the record of blow counts commenced"
],
"proeth:violatesObligation": [],
"proeth:withinCompetence": true,
"rdfs:label": "Test Condition Deviation"
}
Description: Throughout the development of his report, Engineer B did not talk to any representative of Engineer A and made no effort to inquire from contractors, workers, or others on the job to verify or refute his theories.
Temporal Marker: Throughout the development of Engineer B's report interval
Fluent Transitions:
- Unverified Factual Basis for Report
Mental State: deliberate omission
Intended Outcome: Complete the report based only on his own test observations
Foreseen Unintended Effects:
- Unverified theories about why the 19 piles met driving refusal prior to predicted depth
Obligation Engagement:
- Fact-Gathering Diligence
Required Capabilities:
Field classification (triples vs literals)
requiresCapability: Investigative diligence; Professional communicationinitiates: Unverified Factual Basis for ReportraisesObligation: Fact-Gathering Diligence
descriptioncontent: Throughout the development of his report, Engineer B did not talk to any representative of Engineer A and made no effort to inquire from contractors, workers, or others on the job to verify or refute his theories.hasAgentcontent: Engineer BtemporalMarkercontent: Throughout the development of Engineer B's reporteventRoleContextcontent: Test Program SupervisorhasMentalStatecontent: deliberate omissionintendedOutcomecontent: Complete the report based only on his own test observationsforeseenUnintendedEffectscontent: Unverified theories about why the 19 piles met driving refusal prior to predicted depthtextReferencescontent: At no time during the development of Engineer B's report did Engineer B talk to any representative of Engineer A, even though Engineer A's on-site representatives were available to testify as to the accuracy of the pile driving records.; No effort was made by Engineer B to inquire from contractors, workers, or others on the job to verify or refute his theories about why the 19 piles met driving refusal prior to predicted depth.temporalExtentcontent: intervaltemporalSequencecontent: 12withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/71#",
"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/71#Action_Consultation_Omission",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-13T07:28:03.172726+00:00",
"proeth:description": "Throughout the development of his report, Engineer B did not talk to any representative of Engineer A and made no effort to inquire from contractors, workers, or others on the job to verify or refute his theories.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "Test Program Supervisor",
"proeth:foreseenUnintendedEffects": [
"Unverified theories about why the 19 piles met driving refusal prior to predicted depth"
],
"proeth:fulfillsObligation": [],
"proeth:hasAgent": "Engineer B",
"proeth:hasMentalState": "deliberate omission",
"proeth:initiates": [
"Unverified Factual Basis for Report"
],
"proeth:intendedOutcome": "Complete the report based only on his own test observations",
"proeth:raisesObligation": [
"Fact-Gathering Diligence"
],
"proeth:requiresCapability": [
"Investigative diligence",
"Professional communication"
],
"proeth:temporalExtent": "interval",
"proeth:temporalMarker": "Throughout the development of Engineer B\u0027s report",
"proeth:temporalSequence": 12,
"proeth:textReferences": [
"At no time during the development of Engineer B\u0027s report did Engineer B talk to any representative of Engineer A, even though Engineer A\u0027s on-site representatives were available to testify as to the accuracy of the pile driving records.",
"No effort was made by Engineer B to inquire from contractors, workers, or others on the job to verify or refute his theories about why the 19 piles met driving refusal prior to predicted depth."
],
"proeth:violatesObligation": [],
"proeth:withinCompetence": true,
"rdfs:label": "Consultation Omission"
}
Description: Engineer B chose not to examine the pile driving records, justifying the exclusion as outside the scope of work, and thereby denied himself the opportunity to present a rationale for discounting their value.
Temporal Marker: During the development of the report instant
Fluent Transitions:
- Pile Driving Records Excluded from Analysis
Mental State: deliberate scope limitation
Intended Outcome: Confine the analysis to the test pile program alone
Foreseen Unintended Effects:
- Excluding record evidence indicating the piles were driven to essential refusal
Obligation Engagement:
- Include All Relevant and Pertinent Information
- Fact-Gathering Diligence
Required Capabilities:
Field classification (triples vs literals)
requiresCapability: Review of pile driving recordsinitiates: Pile Driving Records Excluded from AnalysisraisesObligation: Include All Relevant and Pertinent Information; Fact-Gathering Diligence
descriptioncontent: Engineer B chose not to examine the pile driving records, justifying the exclusion as outside the scope of work, and thereby denied himself the opportunity to present a rationale for discounting their value.hasAgentcontent: Engineer BtemporalMarkercontent: During the development of the reporteventRoleContextcontent: Test Program SupervisorhasMentalStatecontent: deliberate scope limitationintendedOutcomecontent: Confine the analysis to the test pile program aloneforeseenUnintendedEffectscontent: Excluding record evidence indicating the piles were driven to essential refusaltextReferencescontent: We didn't look at the pile driving records because it was not in our scope of work.temporalExtentcontent: instanttemporalSequencecontent: 13withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/71#",
"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/71#Action_Records_Exclusion_Decision",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-13T07:28:03.172767+00:00",
"proeth:description": "Engineer B chose not to examine the pile driving records, justifying the exclusion as outside the scope of work, and thereby denied himself the opportunity to present a rationale for discounting their value.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "Test Program Supervisor",
"proeth:foreseenUnintendedEffects": [
"Excluding record evidence indicating the piles were driven to essential refusal"
],
"proeth:fulfillsObligation": [],
"proeth:hasAgent": "Engineer B",
"proeth:hasMentalState": "deliberate scope limitation",
"proeth:initiates": [
"Pile Driving Records Excluded from Analysis"
],
"proeth:intendedOutcome": "Confine the analysis to the test pile program alone",
"proeth:raisesObligation": [
"Include All Relevant and Pertinent Information",
"Fact-Gathering Diligence"
],
"proeth:requiresCapability": [
"Review of pile driving records"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "During the development of the report",
"proeth:temporalSequence": 13,
"proeth:textReferences": [
"We didn\u0027t look at the pile driving records because it was not in our scope of work."
],
"proeth:violatesObligation": [],
"proeth:withinCompetence": true,
"rdfs:label": "Records Exclusion Decision"
}
Description: Engineer B issued a concluding report stating that 19 of the 90 piles did not meet the required safety factor, while omitting that the dynamic test equipment had failed, that the 19 piles had been driven to essential refusal, and that wave equation calculations indicated strength several multiples over the load requirements.
Temporal Marker: At the conclusion of the test pile program instant
Fluent Transitions:
- Incomplete Engineering Report in Evidence
- Engineer A Professionally Impugned
Mental State: deliberate selective use of data
Intended Outcome: Support the client municipality's position that the piles failed the design safety factor
Foreseen Unintended Effects:
- Precluding any interpretation that the piles met the factor of safety requirement
- Potentially misdirecting the client's conclusion
Obligation Engagement:
- Include All Relevant and Pertinent Information
- Fact-Gathering Diligence
Required Capabilities:
Field classification (triples vs literals)
violatesObligation: Include All Relevant and Pertinent Information; Fact-Gathering DiligencerequiresCapability: Geotechnical analysis; Engineering report writing; Wave equation calculationinitiates: Incomplete Engineering Report in Evidence; Engineer A Professionally Impugned
descriptioncontent: Engineer B issued a concluding report stating that 19 of the 90 piles did not meet the required safety factor, while omitting that the dynamic test equipment had failed, that the 19 piles had been driven to essential refusal, and that wave equation calculations indicated strength several multiples over the load requirements.hasAgentcontent: Engineer BtemporalMarkercontent: At the conclusion of the test pile programeventRoleContextcontent: Test Program SupervisorhasMentalStatecontent: deliberate selective use of dataintendedOutcomecontent: Support the client municipality's position that the piles failed the design safety factorforeseenUnintendedEffectscontent: Precluding any interpretation that the piles met the factor of safety requirement; Potentially misdirecting the client's conclusiontextReferencescontent: Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations.; Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal and that, applying accepted wave equation calculations, the piles would have indicated a strength several multiples over the calculated load requirements. Additionally, Engineer B did not report that the dynamic test equipment had failed.temporalExtentcontent: instanttemporalSequencecontent: 14withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/71#",
"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/71#Action_Selective_Report_Issuance",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-13T07:28:03.172747+00:00",
"proeth:description": "Engineer B issued a concluding report stating that 19 of the 90 piles did not meet the required safety factor, while omitting that the dynamic test equipment had failed, that the 19 piles had been driven to essential refusal, and that wave equation calculations indicated strength several multiples over the load requirements.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "Test Program Supervisor",
"proeth:foreseenUnintendedEffects": [
"Precluding any interpretation that the piles met the factor of safety requirement",
"Potentially misdirecting the client\u0027s conclusion"
],
"proeth:fulfillsObligation": [],
"proeth:hasAgent": "Engineer B",
"proeth:hasMentalState": "deliberate selective use of data",
"proeth:initiates": [
"Incomplete Engineering Report in Evidence",
"Engineer A Professionally Impugned"
],
"proeth:intendedOutcome": "Support the client municipality\u0027s position that the piles failed the design safety factor",
"proeth:raisesObligation": [],
"proeth:requiresCapability": [
"Geotechnical analysis",
"Engineering report writing",
"Wave equation calculation"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "At the conclusion of the test pile program",
"proeth:temporalSequence": 14,
"proeth:textReferences": [
"Engineer B\u0027s concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations.",
"Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal and that, applying accepted wave equation calculations, the piles would have indicated a strength several multiples over the calculated load requirements. Additionally, Engineer B did not report that the dynamic test equipment had failed."
],
"proeth:violatesObligation": [
"Include All Relevant and Pertinent Information",
"Fact-Gathering Diligence"
],
"proeth:withinCompetence": true,
"rdfs:label": "Selective Report Issuance"
}
Description: When queried by Engineer A after the report was issued, Engineer B offered shifting explanations, saying the driving records looked suspicious and were not believed, after previously saying the records were outside his scope of work.
Temporal Marker: After the report was issued, when queried by Engineer A instant
Fluent Transitions:
- Inconsistent Justification of Report Basis
Mental State: defensive rationalization
Intended Outcome: Justify the report's exclusion of the pile driving records
Foreseen Unintended Effects:
- Inconsistent explanations undermining the credibility of the report's basis
Obligation Engagement:
- Include All Relevant and Pertinent Information
Required Capabilities:
Field classification (triples vs literals)
violatesObligation: Include All Relevant and Pertinent InformationrequiresCapability: Professional communicationinitiates: Inconsistent Justification of Report Basis
descriptioncontent: When queried by Engineer A after the report was issued, Engineer B offered shifting explanations, saying the driving records looked suspicious and were not believed, after previously saying the records were outside his scope of work.hasAgentcontent: Engineer BtemporalMarkercontent: After the report was issued, when queried by Engineer AeventRoleContextcontent: Test Program SupervisorhasMentalStatecontent: defensive rationalizationintendedOutcomecontent: Justify the report's exclusion of the pile driving recordsforeseenUnintendedEffectscontent: Inconsistent explanations undermining the credibility of the report's basistextReferencescontent: We just did not believe the driving records and there was also the issue of whether the pile was vented to allow air to escape from below a closure plate that was included in the pile to separate the concrete fill in the pile from the clay. The driving records look suspicious.; Previously, Engineer B had said, "We didn't look at the pile driving records because it was not in our scope of work."temporalExtentcontent: instanttemporalSequencecontent: 15withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/71#",
"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/71#Action_Post-Report_Justification",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-13T07:28:03.172789+00:00",
"proeth:description": "When queried by Engineer A after the report was issued, Engineer B offered shifting explanations, saying the driving records looked suspicious and were not believed, after previously saying the records were outside his scope of work.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "Test Program Supervisor",
"proeth:foreseenUnintendedEffects": [
"Inconsistent explanations undermining the credibility of the report\u0027s basis"
],
"proeth:fulfillsObligation": [],
"proeth:hasAgent": "Engineer B",
"proeth:hasMentalState": "defensive rationalization",
"proeth:initiates": [
"Inconsistent Justification of Report Basis"
],
"proeth:intendedOutcome": "Justify the report\u0027s exclusion of the pile driving records",
"proeth:raisesObligation": [],
"proeth:requiresCapability": [
"Professional communication"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "After the report was issued, when queried by Engineer A",
"proeth:temporalSequence": 15,
"proeth:textReferences": [
"We just did not believe the driving records and there was also the issue of whether the pile was vented to allow air to escape from below a closure plate that was included in the pile to separate the concrete fill in the pile from the clay. The driving records look suspicious.",
"Previously, Engineer B had said, \"We didn\u0027t look at the pile driving records because it was not in our scope of work.\""
],
"proeth:violatesObligation": [
"Include All Relevant and Pertinent Information"
],
"proeth:withinCompetence": true,
"rdfs:label": "Post-Report Justification"
}
Description: Engineer A's independent geotechnical consultant testified and showed that the dynamic test equipment had failed and that the test piles were not driven to the required depth of penetration.
Temporal Marker: After the test pile program, during proceedings instant
Fluent Transitions:
- Test Deficiencies Disclosed on Record
Mental State: deliberate
Intended Outcome: Place the equipment failure and test deficiencies on the record
Obligation Engagement:
- Include All Relevant and Pertinent Information
Guided By Principles:
- Exponents of All Available Technical Facts
Required Capabilities:
Field classification (triples vs literals)
fulfillsObligation: Include All Relevant and Pertinent InformationguidedByPrinciple: Exponents of All Available Technical FactsrequiresCapability: Geotechnical analysis; Expert testimonyinitiates: Test Deficiencies Disclosed on Record
descriptioncontent: Engineer A's independent geotechnical consultant testified and showed that the dynamic test equipment had failed and that the test piles were not driven to the required depth of penetration.hasAgentcontent: Independent Geotechnical ConsultanttemporalMarkercontent: After the test pile program, during proceedingseventRoleContextcontent: retained by Engineer AhasMentalStatecontent: deliberateintendedOutcomecontent: Place the equipment failure and test deficiencies on the recordtextReferencescontent: The geotechnical consultant testified and showed that dynamic test equipment had failed during the test and that the test piles were not driven to the same depth of penetration that apparently was required for the plug to form in the original piles.temporalExtentcontent: instanttemporalSequencecontent: 16withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/71#",
"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/71#Action_Test_Deficiency_Testimony",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-13T07:28:03.172700+00:00",
"proeth:description": "Engineer A\u0027s independent geotechnical consultant testified and showed that the dynamic test equipment had failed and that the test piles were not driven to the required depth of penetration.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "retained by Engineer A",
"proeth:fulfillsObligation": [
"Include All Relevant and Pertinent Information"
],
"proeth:guidedByPrinciple": [
"Exponents of All Available Technical Facts"
],
"proeth:hasAgent": "Independent Geotechnical Consultant",
"proeth:hasMentalState": "deliberate",
"proeth:initiates": [
"Test Deficiencies Disclosed on Record"
],
"proeth:intendedOutcome": "Place the equipment failure and test deficiencies on the record",
"proeth:raisesObligation": [],
"proeth:requiresCapability": [
"Geotechnical analysis",
"Expert testimony"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "After the test pile program, during proceedings",
"proeth:temporalSequence": 16,
"proeth:textReferences": [
"The geotechnical consultant testified and showed that dynamic test equipment had failed during the test and that the test piles were not driven to the same depth of penetration that apparently was required for the plug to form in the original piles."
],
"proeth:violatesObligation": [],
"proeth:withinCompetence": true,
"rdfs:label": "Test Deficiency Testimony"
}
Description: Engineer A and the municipality settled the contractor's extra claim through mediation and shared the $300,000 settlement cost.
Temporal Marker: After construction, during litigation with the contractor instant
Fluent Transitions:
- Adversarial Relationship Between Municipality and Engineer A
- Contractor Claim Litigation
Mental State: deliberate
Intended Outcome: Resolve the contractor's claim without further litigation
Foreseen Unintended Effects:
- Remaining dispute over how the settlement cost should be shared between Engineer A and the municipality
Required Capabilities:
Field classification (triples vs literals)
requiresCapability: Dispute resolution judgmentinitiates: Adversarial Relationship Between Municipality and Engineer Aterminates: Contractor Claim Litigation
descriptioncontent: Engineer A and the municipality settled the contractor's extra claim through mediation and shared the $300,000 settlement cost.hasAgentcontent: Engineer A and the MunicipalitytemporalMarkercontent: After construction, during litigation with the contractoreventRoleContextcontent: Co-defendantshasMentalStatecontent: deliberateintendedOutcomecontent: Resolve the contractor's claim without further litigationforeseenUnintendedEffectscontent: Remaining dispute over how the settlement cost should be shared between Engineer A and the municipalitytextReferencescontent: The claim was settled by mediation. Engineer A and the municipality shared the cost of the settlement with the contractor for $300,000.temporalExtentcontent: instanttemporalSequencecontent: 17withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/71#",
"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/71#Action_Mediated_Settlement_Decision",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-13T07:28:03.172534+00:00",
"proeth:description": "Engineer A and the municipality settled the contractor\u0027s extra claim through mediation and shared the $300,000 settlement cost.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "Co-defendants",
"proeth:foreseenUnintendedEffects": [
"Remaining dispute over how the settlement cost should be shared between Engineer A and the municipality"
],
"proeth:hasAgent": "Engineer A and the Municipality",
"proeth:hasMentalState": "deliberate",
"proeth:initiates": [
"Adversarial Relationship Between Municipality and Engineer A"
],
"proeth:intendedOutcome": "Resolve the contractor\u0027s claim without further litigation",
"proeth:requiresCapability": [
"Dispute resolution judgment"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "After construction, during litigation with the contractor",
"proeth:temporalSequence": 17,
"proeth:terminates": [
"Contractor Claim Litigation"
],
"proeth:textReferences": [
"The claim was settled by mediation. Engineer A and the municipality shared the cost of the settlement with the contractor for $300,000."
],
"proeth:withinCompetence": true,
"rdfs:label": "Mediated Settlement Decision"
}
Extracted Events (5)
Occurrences that trigger ethical considerations and state changesDescription: During original construction driving, many piles, including the nineteen later cited by Engineer B, met essential refusal before reaching predicted penetration depth and did not initially show driving resistance sufficient for the design load requirements.
Temporal Marker: During original pile driving at construction interval
Fluent Transitions:
- Disputed Pile Adequacy
Field classification (triples vs literals)
initiates: Disputed Pile Adequacy
descriptioncontent: During original construction driving, many piles, including the nineteen later cited by Engineer B, met essential refusal before reaching predicted penetration depth and did not initially show driving resistance sufficient for the design load requirements.temporalMarkercontent: During original pile driving at constructiontextReferencescontent: many of the piles did not, at the time of initial driving, meet driving resistance sufficient to satisfy the load carrying requirements of the design calculations; the 19 piles met driving refusal prior to predicted deptheventTypecontent: exogenoustemporalExtentcontent: intervaltemporalSequencecontent: 2confidenceassessment: 0.85
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/71#",
"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/71#Event_Premature_Driving_Refusal",
"@type": "proeth:Event",
"generatedAtTime": "2026-07-13T07:28:03.172915+00:00",
"proeth:confidence": "0.85",
"proeth:description": "During original construction driving, many piles, including the nineteen later cited by Engineer B, met essential refusal before reaching predicted penetration depth and did not initially show driving resistance sufficient for the design load requirements.",
"proeth:discoveredInSection": "facts",
"proeth:eventType": "exogenous",
"proeth:initiates": [
"Disputed Pile Adequacy"
],
"proeth:temporalExtent": "interval",
"proeth:temporalMarker": "During original pile driving at construction",
"proeth:temporalSequence": 2,
"proeth:textReferences": [
"many of the piles did not, at the time of initial driving, meet driving resistance sufficient to satisfy the load carrying requirements of the design calculations",
"the 19 piles met driving refusal prior to predicted depth"
],
"rdfs:label": "Premature Driving Refusal"
}
Description: Following construction of the dock, the contractor filed an extra claim and sued both Engineer A and the municipality, initiating the dispute that led to mediation.
Temporal Marker: Following construction instant
Fluent Transitions:
- Litigation State
- Adversarial Relationship
Field classification (triples vs literals)
initiates: Litigation State; Adversarial Relationship
descriptioncontent: Following construction of the dock, the contractor filed an extra claim and sued both Engineer A and the municipality, initiating the dispute that led to mediation.temporalMarkercontent: Following constructiontextReferencescontent: Following construction, there was a contractor's extra claim and Engineer A and the municipality were both sued by the contractor.eventTypecontent: exogenoustemporalExtentcontent: instanttemporalSequencecontent: 3confidenceassessment: 0.93
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/71#",
"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/71#Event_Contractor_Claim_Lawsuit",
"@type": "proeth:Event",
"generatedAtTime": "2026-07-13T07:28:03.172882+00:00",
"proeth:confidence": "0.93",
"proeth:description": "Following construction of the dock, the contractor filed an extra claim and sued both Engineer A and the municipality, initiating the dispute that led to mediation.",
"proeth:discoveredInSection": "facts",
"proeth:eventType": "exogenous",
"proeth:initiates": [
"Litigation State",
"Adversarial Relationship"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "Following construction",
"proeth:temporalSequence": 3,
"proeth:textReferences": [
"Following construction, there was a contractor\u0027s extra claim and Engineer A and the municipality were both sued by the contractor."
],
"rdfs:label": "Contractor Claim Lawsuit"
}
Description: The dynamic test equipment failed during the test pile driving program supervised by Engineer B, compromising the completeness and reliability of the test data.
Temporal Marker: During the test pile driving program instant
Fluent Transitions:
- Compromised Test Data
Field classification (triples vs literals)
initiates: Compromised Test Data
descriptioncontent: The dynamic test equipment failed during the test pile driving program supervised by Engineer B, compromising the completeness and reliability of the test data.temporalMarkercontent: During the test pile driving programtextReferencescontent: dynamic test equipment had failed during the test; Engineer B did not report that the dynamic test equipment had failedeventTypecontent: exogenoustemporalExtentcontent: instanttemporalSequencecontent: 9confidenceassessment: 0.95
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/71#",
"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/71#Event_Test_Equipment_Failure",
"@type": "proeth:Event",
"generatedAtTime": "2026-07-13T07:28:03.172939+00:00",
"proeth:confidence": "0.95",
"proeth:description": "The dynamic test equipment failed during the test pile driving program supervised by Engineer B, compromising the completeness and reliability of the test data.",
"proeth:discoveredInSection": "facts",
"proeth:eventType": "exogenous",
"proeth:initiates": [
"Compromised Test Data"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "During the test pile driving program",
"proeth:temporalSequence": 9,
"proeth:textReferences": [
"dynamic test equipment had failed during the test",
"Engineer B did not report that the dynamic test equipment had failed"
],
"rdfs:label": "Test Equipment Failure"
}
Description: After the 30 day set up, the driving hammer was dropped several times to start the hammer before blow counts began, which in the opinion of Engineer A's geotechnical consultant broke the pile bond and undervalued the skin friction value reported by Engineer B's tests.
Temporal Marker: After the 30 day set up, before blow count recording commenced instant
Fluent Transitions:
- Undervalued Skin Friction Data
Caused By Action: Action_Test_Condition_Deviation
Field classification (triples vs literals)
causedByAction: http://proethica.org/ontology/case/71#Action_Test_Condition_Deviationinitiates: Undervalued Skin Friction Data
descriptioncontent: After the 30 day set up, the driving hammer was dropped several times to start the hammer before blow counts began, which in the opinion of Engineer A's geotechnical consultant broke the pile bond and undervalued the skin friction value reported by Engineer B's tests.temporalMarkercontent: After the 30 day set up, before blow count recording commencedtextReferencescontent: after the 30 day set up, the driving hammer was dropped several times to start the hammer before the record of blow counts commenced; this would have broken the pile bond and undervalued the skin friction value reported by Engineer B's testseventTypecontent: outcometemporalExtentcontent: instanttemporalSequencecontent: 10confidenceassessment: 0.8
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/71#",
"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/71#Event_Pile_Bond_Disruption",
"@type": "proeth:Event",
"generatedAtTime": "2026-07-13T07:28:03.172960+00:00",
"proeth:causedByAction": "http://proethica.org/ontology/case/71#Action_Test_Condition_Deviation",
"proeth:confidence": "0.8",
"proeth:description": "After the 30 day set up, the driving hammer was dropped several times to start the hammer before blow counts began, which in the opinion of Engineer A\u0027s geotechnical consultant broke the pile bond and undervalued the skin friction value reported by Engineer B\u0027s tests.",
"proeth:discoveredInSection": "facts",
"proeth:eventType": "outcome",
"proeth:initiates": [
"Undervalued Skin Friction Data"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "After the 30 day set up, before blow count recording commenced",
"proeth:temporalSequence": 10,
"proeth:textReferences": [
"after the 30 day set up, the driving hammer was dropped several times to start the hammer before the record of blow counts commenced",
"this would have broken the pile bond and undervalued the skin friction value reported by Engineer B\u0027s tests"
],
"rdfs:label": "Pile Bond Disruption"
}
Description: Despite the deficiencies in the test program, the test piles after a 30 day set demonstrated the increase in set up strength over time, confirming the premise of Engineer A's design basis testimony.
Temporal Marker: After the 30 day set of the test piles instant
Fluent Transitions:
- Setup Strength Confirmed
Caused By Action: Action_Test_Supervisor_Retention
Field classification (triples vs literals)
causedByAction: http://proethica.org/ontology/case/71#Action_Test_Supervisor_Retentioninitiates: Setup Strength Confirmed
descriptioncontent: Despite the deficiencies in the test program, the test piles after a 30 day set demonstrated the increase in set up strength over time, confirming the premise of Engineer A's design basis testimony.temporalMarkercontent: After the 30 day set of the test pilestextReferencescontent: the test piles were driven and after a 30 day set, the increase in set up strength with time was confirmedeventTypecontent: outcometemporalExtentcontent: instanttemporalSequencecontent: 11confidenceassessment: 0.9
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/71#",
"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/71#Event_Strength_Gain_Confirmation",
"@type": "proeth:Event",
"generatedAtTime": "2026-07-13T07:28:03.172982+00:00",
"proeth:causedByAction": "http://proethica.org/ontology/case/71#Action_Test_Supervisor_Retention",
"proeth:confidence": "0.9",
"proeth:description": "Despite the deficiencies in the test program, the test piles after a 30 day set demonstrated the increase in set up strength over time, confirming the premise of Engineer A\u0027s design basis testimony.",
"proeth:discoveredInSection": "facts",
"proeth:eventType": "outcome",
"proeth:initiates": [
"Setup Strength Confirmed"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "After the 30 day set of the test piles",
"proeth:temporalSequence": 11,
"proeth:textReferences": [
"the test piles were driven and after a 30 day set, the increase in set up strength with time was confirmed"
],
"rdfs:label": "Strength Gain Confirmation"
}
Causal Chains (9)
NESS test analysis: Necessary Element of Sufficient SetCausal Language: To test this, the municipality retained Engineer B to supervise the driving of several test piles to see whether the piles would gain sufficient strength to meet the design calculation requirements.
Necessary Factors (NESS):
- Engineer A's testimony that piles would gain sufficient strength within 30 days
- Municipality's contrary expert testimony that piles failed initial driving resistance
- A factual dispute testable by a pile driving program
Sufficient Factors:
- The conflict between Engineer A's set-up strength claim and the municipality expert's testimony was sufficient to prompt a test pile program under Engineer B
Responsibility Attribution:
Agent: Municipality
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Expert Witness Retention
Municipality's expert testifies many piles did not meet driving resistance at initial driving -
Design Basis Testimony
Engineer A testifies the geotechnical report predicted sufficient strength gain within 30 days -
Test Supervisor Retention
Municipality retains Engineer B to supervise driving of test piles to test the claim -
Independent Observer Retention
Engineer A retains an independent geotechnical consultant to observe the test
Field classification (triples vs literals)
cause: Design Basis Testimonyeffect: Test Supervisor RetentionresponsibleAgent: Municipality
causalLanguagecontent: To test this, the municipality retained Engineer B to supervise the driving of several test piles to see whether the piles would gain sufficient strength to meet the design calculation requirements.necessaryFactorscontent: Engineer A's testimony that piles would gain sufficient strength within 30 days; Municipality's contrary expert testimony that piles failed initial driving resistance; A factual dispute testable by a pile driving programsufficientFactorscontent: The conflict between Engineer A's set-up strength claim and the municipality expert's testimony was sufficient to prompt a test pile program under Engineer Bcounterfactualcontent: Without Engineer A's testimony about 30-day strength gain, there would have been no specific hypothesis to test and no retention of Engineer BagentKnowledgecontent: Municipality knew Engineer A's defense rested on the geotechnical firm's predicted set-up strength gain and sought to test that claiminterveningFactorscontent: Availability of Engineer B to supervise the test programcausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Expert Witness Retention', 'proeth:description': "Municipality's expert testifies many piles did not meet driving resistance at initial driving"}; {'proeth:step': 2, 'proeth:element': 'Design Basis Testimony', 'proeth:description': 'Engineer A testifies the geotechnical report predicted sufficient strength gain within 30 days'}; {'proeth:step': 3, 'proeth:element': 'Test Supervisor Retention', 'proeth:description': 'Municipality retains Engineer B to supervise driving of test piles to test the claim'}; {'proeth:step': 4, 'proeth:element': 'Independent Observer Retention', 'proeth:description': 'Engineer A retains an independent geotechnical consultant to observe the test'}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/71#",
"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/71#CausalChain_3",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T07:28:03.173092+00:00",
"proeth:agentKnowledge": "Municipality knew Engineer A\u0027s defense rested on the geotechnical firm\u0027s predicted set-up strength gain and sought to test that claim",
"proeth:causalLanguage": "To test this, the municipality retained Engineer B to supervise the driving of several test piles to see whether the piles would gain sufficient strength to meet the design calculation requirements.",
"proeth:causalSequence": [
{
"proeth:description": "Municipality\u0027s expert testifies many piles did not meet driving resistance at initial driving",
"proeth:element": "Expert Witness Retention",
"proeth:step": 1
},
{
"proeth:description": "Engineer A testifies the geotechnical report predicted sufficient strength gain within 30 days",
"proeth:element": "Design Basis Testimony",
"proeth:step": 2
},
{
"proeth:description": "Municipality retains Engineer B to supervise driving of test piles to test the claim",
"proeth:element": "Test Supervisor Retention",
"proeth:step": 3
},
{
"proeth:description": "Engineer A retains an independent geotechnical consultant to observe the test",
"proeth:element": "Independent Observer Retention",
"proeth:step": 4
}
],
"proeth:cause": "Design Basis Testimony",
"proeth:counterfactual": "Without Engineer A\u0027s testimony about 30-day strength gain, there would have been no specific hypothesis to test and no retention of Engineer B",
"proeth:discoveredInSection": "facts",
"proeth:effect": "Test Supervisor Retention",
"proeth:interveningFactors": [
"Availability of Engineer B to supervise the test program"
],
"proeth:necessaryFactors": [
"Engineer A\u0027s testimony that piles would gain sufficient strength within 30 days",
"Municipality\u0027s contrary expert testimony that piles failed initial driving resistance",
"A factual dispute testable by a pile driving program"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Municipality",
"proeth:sufficientFactors": [
"The conflict between Engineer A\u0027s set-up strength claim and the municipality expert\u0027s testimony was sufficient to prompt a test pile program under Engineer B"
],
"proeth:withinAgentControl": true
}
Causal Language: Following construction, there was a contractor's extra claim and Engineer A and the municipality were both sued by the contractor. The claim was settled by mediation.
Necessary Factors (NESS):
- Contractor filing an extra claim against both parties
- Lawsuit naming both Engineer A and the municipality
- Willingness of parties to resolve the claim through mediation
Sufficient Factors:
- The lawsuit combined with both parties' exposure to liability was enough to drive them into a mediated settlement
Responsibility Attribution:
Agent: Contractor
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Design Engagement Acceptance
Engineer A designs the dock on a foundation of 90 piles for the municipality -
Contractor Claim Lawsuit
Contractor files an extra claim and sues both Engineer A and the municipality -
Mediated Settlement Decision
Engineer A and the municipality settle by mediation and share the $300,000 cost
Field classification (triples vs literals)
cause: Contractor Claim Lawsuiteffect: Mediated Settlement DecisionresponsibleAgent: Contractor
causalLanguagecontent: Following construction, there was a contractor's extra claim and Engineer A and the municipality were both sued by the contractor. The claim was settled by mediation.necessaryFactorscontent: Contractor filing an extra claim against both parties; Lawsuit naming both Engineer A and the municipality; Willingness of parties to resolve the claim through mediationsufficientFactorscontent: The lawsuit combined with both parties' exposure to liability was enough to drive them into a mediated settlementcounterfactualcontent: Without the contractor's claim and lawsuit, there would have been no mediation and no $300,000 shared settlementagentKnowledgecontent: Contractor believed it had grounds for an extra claim arising from the dock constructioninterveningFactorscontent: Decision by Engineer A and the municipality to settle rather than litigatecausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Design Engagement Acceptance', 'proeth:description': 'Engineer A designs the dock on a foundation of 90 piles for the municipality'}; {'proeth:step': 2, 'proeth:element': 'Contractor Claim Lawsuit', 'proeth:description': 'Contractor files an extra claim and sues both Engineer A and the municipality'}; {'proeth:step': 3, 'proeth:element': 'Mediated Settlement Decision', 'proeth:description': 'Engineer A and the municipality settle by mediation and share the $300,000 cost'}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/71#",
"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/71#CausalChain_1",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T07:28:03.173038+00:00",
"proeth:agentKnowledge": "Contractor believed it had grounds for an extra claim arising from the dock construction",
"proeth:causalLanguage": "Following construction, there was a contractor\u0027s extra claim and Engineer A and the municipality were both sued by the contractor. The claim was settled by mediation.",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A designs the dock on a foundation of 90 piles for the municipality",
"proeth:element": "Design Engagement Acceptance",
"proeth:step": 1
},
{
"proeth:description": "Contractor files an extra claim and sues both Engineer A and the municipality",
"proeth:element": "Contractor Claim Lawsuit",
"proeth:step": 2
},
{
"proeth:description": "Engineer A and the municipality settle by mediation and share the $300,000 cost",
"proeth:element": "Mediated Settlement Decision",
"proeth:step": 3
}
],
"proeth:cause": "Contractor Claim Lawsuit",
"proeth:counterfactual": "Without the contractor\u0027s claim and lawsuit, there would have been no mediation and no $300,000 shared settlement",
"proeth:discoveredInSection": "facts",
"proeth:effect": "Mediated Settlement Decision",
"proeth:interveningFactors": [
"Decision by Engineer A and the municipality to settle rather than litigate"
],
"proeth:necessaryFactors": [
"Contractor filing an extra claim against both parties",
"Lawsuit naming both Engineer A and the municipality",
"Willingness of parties to resolve the claim through mediation"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Contractor",
"proeth:sufficientFactors": [
"The lawsuit combined with both parties\u0027 exposure to liability was enough to drive them into a mediated settlement"
],
"proeth:withinAgentControl": true
}
Causal Language: In this case, an adversarial relationship is established between the municipality and Engineer A to resolve the sharing of a settlement cost between the two.
Necessary Factors (NESS):
- Existence of a settlement cost to be apportioned between Engineer A and the municipality
- Adversarial posture between the two parties over responsibility
- Municipality's interest in shifting liability onto Engineer A
Sufficient Factors:
- The adversarial cost-sharing dispute was sufficient motivation for the municipality to bring in expert witnesses to support its case
Responsibility Attribution:
Agent: Municipality
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Contractor Claim Lawsuit
Lawsuit places Engineer A and the municipality jointly at risk -
Mediated Settlement Decision
Parties settle and must apportion the $300,000 cost, creating an adversarial relationship -
Expert Witness Retention
Municipality brings in expert witnesses to support its case that many piles did not meet driving resistance requirements
Field classification (triples vs literals)
cause: Mediated Settlement Decisioneffect: Expert Witness RetentionresponsibleAgent: Municipality
causalLanguagecontent: In this case, an adversarial relationship is established between the municipality and Engineer A to resolve the sharing of a settlement cost between the two.necessaryFactorscontent: Existence of a settlement cost to be apportioned between Engineer A and the municipality; Adversarial posture between the two parties over responsibility; Municipality's interest in shifting liability onto Engineer AsufficientFactorscontent: The adversarial cost-sharing dispute was sufficient motivation for the municipality to bring in expert witnesses to support its casecounterfactualcontent: Without the settlement cost dispute, the municipality would have had no reason to retain expert witnesses against Engineer AagentKnowledgecontent: Municipality knew it shared settlement liability and sought expert testimony to support its position that the piles were deficientinterveningFactorscontent: Mediation procedure permitting expert testimonycausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Contractor Claim Lawsuit', 'proeth:description': 'Lawsuit places Engineer A and the municipality jointly at risk'}; {'proeth:step': 2, 'proeth:element': 'Mediated Settlement Decision', 'proeth:description': 'Parties settle and must apportion the $300,000 cost, creating an adversarial relationship'}; {'proeth:step': 3, 'proeth:element': 'Expert Witness Retention', 'proeth:description': 'Municipality brings in expert witnesses to support its case that many piles did not meet driving resistance requirements'}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/71#",
"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/71#CausalChain_2",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T07:28:03.173071+00:00",
"proeth:agentKnowledge": "Municipality knew it shared settlement liability and sought expert testimony to support its position that the piles were deficient",
"proeth:causalLanguage": "In this case, an adversarial relationship is established between the municipality and Engineer A to resolve the sharing of a settlement cost between the two.",
"proeth:causalSequence": [
{
"proeth:description": "Lawsuit places Engineer A and the municipality jointly at risk",
"proeth:element": "Contractor Claim Lawsuit",
"proeth:step": 1
},
{
"proeth:description": "Parties settle and must apportion the $300,000 cost, creating an adversarial relationship",
"proeth:element": "Mediated Settlement Decision",
"proeth:step": 2
},
{
"proeth:description": "Municipality brings in expert witnesses to support its case that many piles did not meet driving resistance requirements",
"proeth:element": "Expert Witness Retention",
"proeth:step": 3
}
],
"proeth:cause": "Mediated Settlement Decision",
"proeth:counterfactual": "Without the settlement cost dispute, the municipality would have had no reason to retain expert witnesses against Engineer A",
"proeth:discoveredInSection": "discussion",
"proeth:effect": "Expert Witness Retention",
"proeth:interveningFactors": [
"Mediation procedure permitting expert testimony"
],
"proeth:necessaryFactors": [
"Existence of a settlement cost to be apportioned between Engineer A and the municipality",
"Adversarial posture between the two parties over responsibility",
"Municipality\u0027s interest in shifting liability onto Engineer A"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Municipality",
"proeth:sufficientFactors": [
"The adversarial cost-sharing dispute was sufficient motivation for the municipality to bring in expert witnesses to support its case"
],
"proeth:withinAgentControl": true
}
Causal Language: Also, after the 30 day set up, the driving hammer was dropped several times to start the hammer before the record of blow counts commenced. In the opinion of Engineer A's geotechnical consultant, this would have broken the pile bond and undervalued the skin friction value reported by Engineer B's tests.
Necessary Factors (NESS):
- Hammer dropped several times before blow counts commenced
- Test piles subjected to conditions differing from original driving (vibratory hammer, insufficient penetration depth)
- 30-day set-up period during which pile bond formed
Sufficient Factors:
- Dropping the hammer several times after the 30-day set-up was sufficient to break the pile bond and undervalue reported skin friction
Responsibility Attribution:
Agent: Engineer B
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Test Supervisor Retention
Engineer B is retained to supervise the test pile program -
Test Condition Deviation
Vibratory hammer used, piles not driven to required penetration, hammer dropped several times before blow counts -
Pile Bond Disruption
Pile bond broken, undervaluing the skin friction value reported by Engineer B's tests -
Selective Report Issuance
Engineer B's report concludes 19 piles fail the safety factor based on undervalued skin friction data
Field classification (triples vs literals)
cause: Test Condition Deviationeffect: Pile Bond DisruptionresponsibleAgent: Engineer B
causalLanguagecontent: Also, after the 30 day set up, the driving hammer was dropped several times to start the hammer before the record of blow counts commenced. In the opinion of Engineer A's geotechnical consultant, this would have broken the pile bond and undervalued the skin friction value reported by Engineer B's tests.necessaryFactorscontent: Hammer dropped several times before blow counts commenced; Test piles subjected to conditions differing from original driving (vibratory hammer, insufficient penetration depth); 30-day set-up period during which pile bond formedsufficientFactorscontent: Dropping the hammer several times after the 30-day set-up was sufficient to break the pile bond and undervalue reported skin frictioncounterfactualcontent: Had driving conditions been duplicated and the hammer not dropped before recording, the pile bond would have remained intact and skin friction values would not have been undervaluedagentKnowledgecontent: As test supervisor, Engineer B was responsible for the test methodology, including hammer type, penetration depth, and start procedureinterveningFactorscontent: Dynamic test equipment failure during the testcausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Test Supervisor Retention', 'proeth:description': 'Engineer B is retained to supervise the test pile program'}; {'proeth:step': 2, 'proeth:element': 'Test Condition Deviation', 'proeth:description': 'Vibratory hammer used, piles not driven to required penetration, hammer dropped several times before blow counts'}; {'proeth:step': 3, 'proeth:element': 'Pile Bond Disruption', 'proeth:description': "Pile bond broken, undervaluing the skin friction value reported by Engineer B's tests"}; {'proeth:step': 4, 'proeth:element': 'Selective Report Issuance', 'proeth:description': "Engineer B's report concludes 19 piles fail the safety factor based on undervalued skin friction data"}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/71#",
"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/71#CausalChain_4",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T07:28:03.173112+00:00",
"proeth:agentKnowledge": "As test supervisor, Engineer B was responsible for the test methodology, including hammer type, penetration depth, and start procedure",
"proeth:causalLanguage": "Also, after the 30 day set up, the driving hammer was dropped several times to start the hammer before the record of blow counts commenced. In the opinion of Engineer A\u0027s geotechnical consultant, this would have broken the pile bond and undervalued the skin friction value reported by Engineer B\u0027s tests.",
"proeth:causalSequence": [
{
"proeth:description": "Engineer B is retained to supervise the test pile program",
"proeth:element": "Test Supervisor Retention",
"proeth:step": 1
},
{
"proeth:description": "Vibratory hammer used, piles not driven to required penetration, hammer dropped several times before blow counts",
"proeth:element": "Test Condition Deviation",
"proeth:step": 2
},
{
"proeth:description": "Pile bond broken, undervaluing the skin friction value reported by Engineer B\u0027s tests",
"proeth:element": "Pile Bond Disruption",
"proeth:step": 3
},
{
"proeth:description": "Engineer B\u0027s report concludes 19 piles fail the safety factor based on undervalued skin friction data",
"proeth:element": "Selective Report Issuance",
"proeth:step": 4
}
],
"proeth:cause": "Test Condition Deviation",
"proeth:counterfactual": "Had driving conditions been duplicated and the hammer not dropped before recording, the pile bond would have remained intact and skin friction values would not have been undervalued",
"proeth:discoveredInSection": "facts",
"proeth:effect": "Pile Bond Disruption",
"proeth:interveningFactors": [
"Dynamic test equipment failure during the test"
],
"proeth:necessaryFactors": [
"Hammer dropped several times before blow counts commenced",
"Test piles subjected to conditions differing from original driving (vibratory hammer, insufficient penetration depth)",
"30-day set-up period during which pile bond formed"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer B",
"proeth:sufficientFactors": [
"Dropping the hammer several times after the 30-day set-up was sufficient to break the pile bond and undervalue reported skin friction"
],
"proeth:withinAgentControl": true
}
Causal Language: The geotechnical consultant testified and showed that dynamic test equipment had failed during the test and that the test piles were not driven to the same depth of penetration that apparently was required for the plug to form in the original piles.
Necessary Factors (NESS):
- Failure of the dynamic test equipment during the test
- Presence of Engineer A's independent geotechnical consultant as an observer
- Mediation forum allowing the consultant to testify
Sufficient Factors:
- The observed equipment failure and test deviations, witnessed by the independent consultant, were sufficient to generate testimony documenting the test's deficiencies
Responsibility Attribution:
Agent: Engineer A (for retaining the observer); Engineer B (for the failed/unreported test conditions)
Type: shared
Within Agent Control:
Yes
Causal Sequence:
-
Independent Observer Retention
Engineer A retains an independent geotechnical consultant to observe the test -
Test Equipment Failure
Dynamic test equipment fails during the test pile program -
Test Deficiency Testimony
Consultant testifies and shows the equipment failure and non-duplicated driving conditions
Field classification (triples vs literals)
cause: Test Equipment Failureeffect: Test Deficiency TestimonyresponsibleAgent: Engineer A (for retaining the observer); Engineer B (for the failed/unreported test conditions)
causalLanguagecontent: The geotechnical consultant testified and showed that dynamic test equipment had failed during the test and that the test piles were not driven to the same depth of penetration that apparently was required for the plug to form in the original piles.necessaryFactorscontent: Failure of the dynamic test equipment during the test; Presence of Engineer A's independent geotechnical consultant as an observer; Mediation forum allowing the consultant to testifysufficientFactorscontent: The observed equipment failure and test deviations, witnessed by the independent consultant, were sufficient to generate testimony documenting the test's deficienciescounterfactualcontent: Had the equipment not failed and conditions been duplicated, there would have been no deficiency to testify about; had no observer been retained, the failure might never have been disclosedagentKnowledgecontent: Engineer A knew independent observation was needed to verify the municipality's test; the consultant directly observed the equipment failureinterveningFactorscontent: Mechanical failure of the dynamic test equipmentcausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Independent Observer Retention', 'proeth:description': 'Engineer A retains an independent geotechnical consultant to observe the test'}; {'proeth:step': 2, 'proeth:element': 'Test Equipment Failure', 'proeth:description': 'Dynamic test equipment fails during the test pile program'}; {'proeth:step': 3, 'proeth:element': 'Test Deficiency Testimony', 'proeth:description': 'Consultant testifies and shows the equipment failure and non-duplicated driving conditions'}responsibilityTypeassessment: sharedwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/71#",
"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/71#CausalChain_5",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T07:28:03.173130+00:00",
"proeth:agentKnowledge": "Engineer A knew independent observation was needed to verify the municipality\u0027s test; the consultant directly observed the equipment failure",
"proeth:causalLanguage": "The geotechnical consultant testified and showed that dynamic test equipment had failed during the test and that the test piles were not driven to the same depth of penetration that apparently was required for the plug to form in the original piles.",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A retains an independent geotechnical consultant to observe the test",
"proeth:element": "Independent Observer Retention",
"proeth:step": 1
},
{
"proeth:description": "Dynamic test equipment fails during the test pile program",
"proeth:element": "Test Equipment Failure",
"proeth:step": 2
},
{
"proeth:description": "Consultant testifies and shows the equipment failure and non-duplicated driving conditions",
"proeth:element": "Test Deficiency Testimony",
"proeth:step": 3
}
],
"proeth:cause": "Test Equipment Failure",
"proeth:counterfactual": "Had the equipment not failed and conditions been duplicated, there would have been no deficiency to testify about; had no observer been retained, the failure might never have been disclosed",
"proeth:discoveredInSection": "facts",
"proeth:effect": "Test Deficiency Testimony",
"proeth:interveningFactors": [
"Mechanical failure of the dynamic test equipment"
],
"proeth:necessaryFactors": [
"Failure of the dynamic test equipment during the test",
"Presence of Engineer A\u0027s independent geotechnical consultant as an observer",
"Mediation forum allowing the consultant to testify"
],
"proeth:responsibilityType": "shared",
"proeth:responsibleAgent": "Engineer A (for retaining the observer); Engineer B (for the failed/unreported test conditions)",
"proeth:sufficientFactors": [
"The observed equipment failure and test deviations, witnessed by the independent consultant, were sufficient to generate testimony documenting the test\u0027s deficiencies"
],
"proeth:withinAgentControl": true
}
Causal Language: Further, by excluding the pile driving records, Engineer B has denied himself the opportunity to present a rational for discounting their value, and thereby to serve his client.
Necessary Factors (NESS):
- Engineer B's decision not to examine the pile driving records as 'not in our scope of work'
- Records showing the 19 piles were driven to essential refusal
- Wave equation calculations that would have indicated strength several multiples over load requirements
Sufficient Factors:
- Excluding the records, combined with reliance solely on skin-friction penetration depth, was sufficient to produce a report concluding 19 piles failed the safety factor without countervailing evidence
Responsibility Attribution:
Agent: Engineer B
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Test Supervisor Retention
Engineer B is retained by the municipality to supervise and report on the test pile program -
Records Exclusion Decision
Engineer B declines to examine the pile driving records, citing scope of work -
Selective Report Issuance
Report states 19 of 90 piles fail the safety factor, omitting refusal data, wave equation results, and the equipment failure -
Misdirected Conclusion
The report 'precludes any interpretation that any or all 90 piles met the factor of safety requirement,' misdirecting the client
Field classification (triples vs literals)
cause: Records Exclusion Decisioneffect: Selective Report IssuanceresponsibleAgent: Engineer B
causalLanguagecontent: Further, by excluding the pile driving records, Engineer B has denied himself the opportunity to present a rational for discounting their value, and thereby to serve his client.necessaryFactorscontent: Engineer B's decision not to examine the pile driving records as 'not in our scope of work'; Records showing the 19 piles were driven to essential refusal; Wave equation calculations that would have indicated strength several multiples over load requirementssufficientFactorscontent: Excluding the records, combined with reliance solely on skin-friction penetration depth, was sufficient to produce a report concluding 19 piles failed the safety factor without countervailing evidencecounterfactualcontent: Had Engineer B examined the driving records, the report would have had to address that the 19 piles were driven to refusal and indicated strength several multiples over the calculated load requirements, likely changing or qualifying the conclusionagentKnowledgecontent: Engineer B knew the driving records existed and later admitted 'We just did not believe the driving records' and 'We didn't look at the pile driving records because it was not in our scope of work'interveningFactorscontent: Adversarial context of the mediation; Narrowly defined scope of work from the municipalitycausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Test Supervisor Retention', 'proeth:description': 'Engineer B is retained by the municipality to supervise and report on the test pile program'}; {'proeth:step': 2, 'proeth:element': 'Records Exclusion Decision', 'proeth:description': 'Engineer B declines to examine the pile driving records, citing scope of work'}; {'proeth:step': 3, 'proeth:element': 'Selective Report Issuance', 'proeth:description': 'Report states 19 of 90 piles fail the safety factor, omitting refusal data, wave equation results, and the equipment failure'}; {'proeth:step': 4, 'proeth:element': 'Misdirected Conclusion', 'proeth:description': "The report 'precludes any interpretation that any or all 90 piles met the factor of safety requirement,' misdirecting the client"}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/71#",
"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/71#CausalChain_6",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T07:28:03.173149+00:00",
"proeth:agentKnowledge": "Engineer B knew the driving records existed and later admitted \u0027We just did not believe the driving records\u0027 and \u0027We didn\u0027t look at the pile driving records because it was not in our scope of work\u0027",
"proeth:causalLanguage": "Further, by excluding the pile driving records, Engineer B has denied himself the opportunity to present a rational for discounting their value, and thereby to serve his client.",
"proeth:causalSequence": [
{
"proeth:description": "Engineer B is retained by the municipality to supervise and report on the test pile program",
"proeth:element": "Test Supervisor Retention",
"proeth:step": 1
},
{
"proeth:description": "Engineer B declines to examine the pile driving records, citing scope of work",
"proeth:element": "Records Exclusion Decision",
"proeth:step": 2
},
{
"proeth:description": "Report states 19 of 90 piles fail the safety factor, omitting refusal data, wave equation results, and the equipment failure",
"proeth:element": "Selective Report Issuance",
"proeth:step": 3
},
{
"proeth:description": "The report \u0027precludes any interpretation that any or all 90 piles met the factor of safety requirement,\u0027 misdirecting the client",
"proeth:element": "Misdirected Conclusion",
"proeth:step": 4
}
],
"proeth:cause": "Records Exclusion Decision",
"proeth:counterfactual": "Had Engineer B examined the driving records, the report would have had to address that the 19 piles were driven to refusal and indicated strength several multiples over the calculated load requirements, likely changing or qualifying the conclusion",
"proeth:discoveredInSection": "discussion",
"proeth:effect": "Selective Report Issuance",
"proeth:interveningFactors": [
"Adversarial context of the mediation",
"Narrowly defined scope of work from the municipality"
],
"proeth:necessaryFactors": [
"Engineer B\u0027s decision not to examine the pile driving records as \u0027not in our scope of work\u0027",
"Records showing the 19 piles were driven to essential refusal",
"Wave equation calculations that would have indicated strength several multiples over load requirements"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer B",
"proeth:sufficientFactors": [
"Excluding the records, combined with reliance solely on skin-friction penetration depth, was sufficient to produce a report concluding 19 piles failed the safety factor without countervailing evidence"
],
"proeth:withinAgentControl": true
}
Causal Language: However, Engineer B’s failure to inquire from the contractor, workers or others on the job is a failure of fact gathering diligence. Engineer B appears to have assumed a responsibility to defend the client municipality by the selective use of data.
Necessary Factors (NESS):
- Engineer B never speaking to any representative of Engineer A despite their availability
- No inquiry made of contractors, workers, or others on the job
- Reliance solely on Engineer B's own deficient test data and theories
Sufficient Factors:
- The failure of fact-gathering diligence, combined with the records exclusion, was sufficient to produce a report based on selective and unverified data
Responsibility Attribution:
Agent: Engineer B
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Test Supervisor Retention
Engineer B begins developing his test program and report -
Consultation Omission
Engineer B makes no effort to verify or refute his theories with Engineer A's representatives, contractors, or workers -
Selective Report Issuance
Report issued on unverified assumptions that the driving records were 'suspicious' -
Post-Report Justification
When queried, Engineer B offers shifting explanations for ignoring the records
Field classification (triples vs literals)
cause: Consultation Omissioneffect: Selective Report IssuanceresponsibleAgent: Engineer B
causalLanguagecontent: However, Engineer B’s failure to inquire from the contractor, workers or others on the job is a failure of fact gathering diligence. Engineer B appears to have assumed a responsibility to defend the client municipality by the selective use of data.necessaryFactorscontent: Engineer B never speaking to any representative of Engineer A despite their availability; No inquiry made of contractors, workers, or others on the job; Reliance solely on Engineer B's own deficient test data and theoriessufficientFactorscontent: The failure of fact-gathering diligence, combined with the records exclusion, was sufficient to produce a report based on selective and unverified datacounterfactualcontent: Had Engineer B consulted Engineer A's on-site representatives or job personnel, the accuracy of the driving records could have been verified and his theories about the 19 piles refuted or confirmed, changing the report's contentagentKnowledgecontent: Engineer A's on-site representatives were available to testify as to the accuracy of the pile driving records; Engineer B chose not to contact them or anyone else on the jobinterveningFactorscontent: Adversarial relationship between the municipality and Engineer AcausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Test Supervisor Retention', 'proeth:description': 'Engineer B begins developing his test program and report'}; {'proeth:step': 2, 'proeth:element': 'Consultation Omission', 'proeth:description': "Engineer B makes no effort to verify or refute his theories with Engineer A's representatives, contractors, or workers"}; {'proeth:step': 3, 'proeth:element': 'Selective Report Issuance', 'proeth:description': "Report issued on unverified assumptions that the driving records were 'suspicious'"}; {'proeth:step': 4, 'proeth:element': 'Post-Report Justification', 'proeth:description': 'When queried, Engineer B offers shifting explanations for ignoring the records'}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/71#",
"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/71#CausalChain_7",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T07:28:03.173166+00:00",
"proeth:agentKnowledge": "Engineer A\u0027s on-site representatives were available to testify as to the accuracy of the pile driving records; Engineer B chose not to contact them or anyone else on the job",
"proeth:causalLanguage": "However, Engineer B\u2019s failure to inquire from the contractor, workers or others on the job is a failure of fact gathering diligence. Engineer B appears to have assumed a responsibility to defend the client municipality by the selective use of data.",
"proeth:causalSequence": [
{
"proeth:description": "Engineer B begins developing his test program and report",
"proeth:element": "Test Supervisor Retention",
"proeth:step": 1
},
{
"proeth:description": "Engineer B makes no effort to verify or refute his theories with Engineer A\u0027s representatives, contractors, or workers",
"proeth:element": "Consultation Omission",
"proeth:step": 2
},
{
"proeth:description": "Report issued on unverified assumptions that the driving records were \u0027suspicious\u0027",
"proeth:element": "Selective Report Issuance",
"proeth:step": 3
},
{
"proeth:description": "When queried, Engineer B offers shifting explanations for ignoring the records",
"proeth:element": "Post-Report Justification",
"proeth:step": 4
}
],
"proeth:cause": "Consultation Omission",
"proeth:counterfactual": "Had Engineer B consulted Engineer A\u0027s on-site representatives or job personnel, the accuracy of the driving records could have been verified and his theories about the 19 piles refuted or confirmed, changing the report\u0027s content",
"proeth:discoveredInSection": "discussion",
"proeth:effect": "Selective Report Issuance",
"proeth:interveningFactors": [
"Adversarial relationship between the municipality and Engineer A"
],
"proeth:necessaryFactors": [
"Engineer B never speaking to any representative of Engineer A despite their availability",
"No inquiry made of contractors, workers, or others on the job",
"Reliance solely on Engineer B\u0027s own deficient test data and theories"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer B",
"proeth:sufficientFactors": [
"The failure of fact-gathering diligence, combined with the records exclusion, was sufficient to produce a report based on selective and unverified data"
],
"proeth:withinAgentControl": true
}
Causal Language: When queried by Engineer A after the report was issued by Engineer B, Engineer B said: "We just did not believe the driving records and there was also the issue of whether the pile was vented to allow air to escape from below a closure plate that was included in the pile to separate the concrete fill in the pile from the clay. The driving records look suspicious."
Necessary Factors (NESS):
- Issuance of a report omitting material facts (refusal data, equipment failure)
- Engineer A's query challenging the report
- Engineer B's lack of a documented rationale within the report itself
Sufficient Factors:
- The report's omissions, once challenged by Engineer A, were sufficient to force Engineer B into after-the-fact, shifting justifications
Responsibility Attribution:
Agent: Engineer B
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Records Exclusion Decision
Engineer B declines to examine the pile driving records -
Selective Report Issuance
Report issued omitting refusal data, wave equation results, and equipment failure -
Query by Engineer A
Engineer A challenges the report's basis after issuance -
Post-Report Justification
Engineer B gives shifting explanations: disbelief of records, venting theory, 'suspicious' records, and earlier scope-of-work excuse
Field classification (triples vs literals)
cause: Selective Report Issuanceeffect: Post-Report JustificationresponsibleAgent: Engineer B
causalLanguagecontent: When queried by Engineer A after the report was issued by Engineer B, Engineer B said: "We just did not believe the driving records and there was also the issue of whether the pile was vented to allow air to escape from below a closure plate that was included in the pile to separate the concrete fill in the pile from the clay. The driving records look suspicious."necessaryFactorscontent: Issuance of a report omitting material facts (refusal data, equipment failure); Engineer A's query challenging the report; Engineer B's lack of a documented rationale within the report itselfsufficientFactorscontent: The report's omissions, once challenged by Engineer A, were sufficient to force Engineer B into after-the-fact, shifting justificationscounterfactualcontent: Had the report included the pile driving records and a rationale for discounting them, Engineer B would not have needed inconsistent post-hoc explanationsagentKnowledgecontent: Engineer B knew the report had excluded the driving records and had previously stated the exclusion was a scope-of-work matterinterveningFactorscontent: Engineer A's decision to query Engineer B after issuancecausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Records Exclusion Decision', 'proeth:description': 'Engineer B declines to examine the pile driving records'}; {'proeth:step': 2, 'proeth:element': 'Selective Report Issuance', 'proeth:description': 'Report issued omitting refusal data, wave equation results, and equipment failure'}; {'proeth:step': 3, 'proeth:element': 'Query by Engineer A', 'proeth:description': "Engineer A challenges the report's basis after issuance"}; {'proeth:step': 4, 'proeth:element': 'Post-Report Justification', 'proeth:description': "Engineer B gives shifting explanations: disbelief of records, venting theory, 'suspicious' records, and earlier scope-of-work excuse"}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/71#",
"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/71#CausalChain_8",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T07:28:03.173185+00:00",
"proeth:agentKnowledge": "Engineer B knew the report had excluded the driving records and had previously stated the exclusion was a scope-of-work matter",
"proeth:causalLanguage": "When queried by Engineer A after the report was issued by Engineer B, Engineer B said: \"We just did not believe the driving records and there was also the issue of whether the pile was vented to allow air to escape from below a closure plate that was included in the pile to separate the concrete fill in the pile from the clay. The driving records look suspicious.\"",
"proeth:causalSequence": [
{
"proeth:description": "Engineer B declines to examine the pile driving records",
"proeth:element": "Records Exclusion Decision",
"proeth:step": 1
},
{
"proeth:description": "Report issued omitting refusal data, wave equation results, and equipment failure",
"proeth:element": "Selective Report Issuance",
"proeth:step": 2
},
{
"proeth:description": "Engineer A challenges the report\u0027s basis after issuance",
"proeth:element": "Query by Engineer A",
"proeth:step": 3
},
{
"proeth:description": "Engineer B gives shifting explanations: disbelief of records, venting theory, \u0027suspicious\u0027 records, and earlier scope-of-work excuse",
"proeth:element": "Post-Report Justification",
"proeth:step": 4
}
],
"proeth:cause": "Selective Report Issuance",
"proeth:counterfactual": "Had the report included the pile driving records and a rationale for discounting them, Engineer B would not have needed inconsistent post-hoc explanations",
"proeth:discoveredInSection": "facts",
"proeth:effect": "Post-Report Justification",
"proeth:interveningFactors": [
"Engineer A\u0027s decision to query Engineer B after issuance"
],
"proeth:necessaryFactors": [
"Issuance of a report omitting material facts (refusal data, equipment failure)",
"Engineer A\u0027s query challenging the report",
"Engineer B\u0027s lack of a documented rationale within the report itself"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer B",
"proeth:sufficientFactors": [
"The report\u0027s omissions, once challenged by Engineer A, were sufficient to force Engineer B into after-the-fact, shifting justifications"
],
"proeth:withinAgentControl": true
}
Causal Language: The opportunity for expert engineering review and interpretation of the pile driving test was effectively denied by Engineer B's report. It is not evident from the facts of the case that Engineer B's selective use of technical fact was inspired by the adversarial circumstance, nor does it matter.
Necessary Factors (NESS):
- Report language precluding any interpretation that the 90 piles met the factor of safety
- Omission of the refusal data and wave equation strength indications
- Omission of the dynamic test equipment failure
Sufficient Factors:
- The select language and omissions of the report were sufficient to foreclose informed expert review and to potentially misdirect the client's conclusion
Responsibility Attribution:
Agent: Engineer B
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Test Condition Deviation
Test conducted under non-duplicated conditions producing compromised data -
Records Exclusion Decision
Countervailing evidence from driving records excluded from consideration -
Selective Report Issuance
Incomplete report concludes 19 piles fail the safety factor -
Denial of Expert Review Opportunity
Report language precludes interpretation that piles met the factor of safety, misdirecting the client and impugning Engineer A
Field classification (triples vs literals)
cause: Selective Report Issuanceeffect: Denial of Expert Review Opportunity (disservice to client municipality)responsibleAgent: Engineer B
causalLanguagecontent: The opportunity for expert engineering review and interpretation of the pile driving test was effectively denied by Engineer B's report. It is not evident from the facts of the case that Engineer B's selective use of technical fact was inspired by the adversarial circumstance, nor does it matter.necessaryFactorscontent: Report language precluding any interpretation that the 90 piles met the factor of safety; Omission of the refusal data and wave equation strength indications; Omission of the dynamic test equipment failuresufficientFactorscontent: The select language and omissions of the report were sufficient to foreclose informed expert review and to potentially misdirect the client's conclusioncounterfactualcontent: A complete report including all relevant and pertinent information would have permitted expert engineering review and served rather than disserved the municipalityagentKnowledgecontent: Engineer B knew of the equipment failure and had access to the driving records showing essential refusal, yet excluded both from the reportinterveningFactorscontent: Adversarial mediation context; Municipality's scope-of-work framingcausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Test Condition Deviation', 'proeth:description': 'Test conducted under non-duplicated conditions producing compromised data'}; {'proeth:step': 2, 'proeth:element': 'Records Exclusion Decision', 'proeth:description': 'Countervailing evidence from driving records excluded from consideration'}; {'proeth:step': 3, 'proeth:element': 'Selective Report Issuance', 'proeth:description': 'Incomplete report concludes 19 piles fail the safety factor'}; {'proeth:step': 4, 'proeth:element': 'Denial of Expert Review Opportunity', 'proeth:description': 'Report language precludes interpretation that piles met the factor of safety, misdirecting the client and impugning Engineer A'}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/71#",
"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/71#CausalChain_9",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T07:28:03.173202+00:00",
"proeth:agentKnowledge": "Engineer B knew of the equipment failure and had access to the driving records showing essential refusal, yet excluded both from the report",
"proeth:causalLanguage": "The opportunity for expert engineering review and interpretation of the pile driving test was effectively denied by Engineer B\u0027s report. It is not evident from the facts of the case that Engineer B\u0027s selective use of technical fact was inspired by the adversarial circumstance, nor does it matter.",
"proeth:causalSequence": [
{
"proeth:description": "Test conducted under non-duplicated conditions producing compromised data",
"proeth:element": "Test Condition Deviation",
"proeth:step": 1
},
{
"proeth:description": "Countervailing evidence from driving records excluded from consideration",
"proeth:element": "Records Exclusion Decision",
"proeth:step": 2
},
{
"proeth:description": "Incomplete report concludes 19 piles fail the safety factor",
"proeth:element": "Selective Report Issuance",
"proeth:step": 3
},
{
"proeth:description": "Report language precludes interpretation that piles met the factor of safety, misdirecting the client and impugning Engineer A",
"proeth:element": "Denial of Expert Review Opportunity",
"proeth:step": 4
}
],
"proeth:cause": "Selective Report Issuance",
"proeth:counterfactual": "A complete report including all relevant and pertinent information would have permitted expert engineering review and served rather than disserved the municipality",
"proeth:discoveredInSection": "discussion",
"proeth:effect": "Denial of Expert Review Opportunity (disservice to client municipality)",
"proeth:interveningFactors": [
"Adversarial mediation context",
"Municipality\u0027s scope-of-work framing"
],
"proeth:necessaryFactors": [
"Report language precluding any interpretation that the 90 piles met the factor of safety",
"Omission of the refusal data and wave equation strength indications",
"Omission of the dynamic test equipment failure"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer B",
"proeth:sufficientFactors": [
"The select language and omissions of the report were sufficient to foreclose informed expert review and to potentially misdirect the client\u0027s conclusion"
],
"proeth:withinAgentControl": true
}
Allen Temporal Relations (18)
Interval algebra relationships with OWL-Time standard properties| From Entity | Allen Relation | To Entity | OWL-Time Property | Evidence |
|---|---|---|---|---|
| Engineer B's 'scope of work' explanation |
before
Entity1 is before Entity2 |
Engineer B's 'did not believe the driving records' explanation |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
Previously, Engineer B had said, 'We didn't look at the pile driving records because it was not in o... [more] |
| Engineer A's design of the dock |
before
Entity1 is before Entity2 |
construction of the dock |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
Engineer A was retained by a municipality to design a dock on a supporting foundation of 90 piles. F... [more] |
| construction of the dock |
before
Entity1 is before Entity2 |
contractor's extra claim and lawsuit |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
Following construction, there was a contractor's extra claim and Engineer A and the municipality wer... [more] |
| contractor's lawsuit |
before
Entity1 is before Entity2 |
settlement by mediation |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
Engineer A and the municipality were both sued by the contractor. The claim was settled by mediation... [more] |
| expert witness testimony |
during
Entity1 occurs entirely within the duration of Entity2 |
mediation |
time:intervalDuring
http://www.w3.org/2006/time#intervalDuring |
During the mediation, the municipality brought in expert witnesses to support their case. |
| initial pile driving |
before
Entity1 is before Entity2 |
expected 30-day strength gain period |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
Engineer A testified that the geotechnical firm's report expected that the piles would gain sufficie... [more] |
| mediation testimony dispute |
before
Entity1 is before Entity2 |
test pile driving program |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
To test this, the municipality retained Engineer B to supervise the driving of several test piles. |
| dynamic test equipment failure |
during
Entity1 occurs entirely within the duration of Entity2 |
test pile driving program |
time:intervalDuring
http://www.w3.org/2006/time#intervalDuring |
dynamic test equipment had failed during the test |
| geotechnical consultant's observation |
during
Entity1 occurs entirely within the duration of Entity2 |
test pile driving program |
time:intervalDuring
http://www.w3.org/2006/time#intervalDuring |
An independent geotechnical consultant was retained by Engineer A to observe the test. |
| test pile driving |
before
Entity1 is before Entity2 |
30-day set-up period |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
the test piles were driven and after a 30 day set, the increase in set up strength with time was con... [more] |
| 30-day set-up period |
before
Entity1 is before Entity2 |
hammer drops to start the hammer |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
after the 30 day set up, the driving hammer was dropped several times to start the hammer |
| hammer drops to start the hammer |
before
Entity1 is before Entity2 |
record of blow counts |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
the driving hammer was dropped several times to start the hammer before the record of blow counts co... [more] |
| hammer drops breaking pile bond |
before
Entity1 is before Entity2 |
skin friction measurement in Engineer B's tests |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
this would have broken the pile bond and undervalued the skin friction value reported by Engineer B'... [more] |
| absence of communication with Engineer A's representatives |
during
Entity1 occurs entirely within the duration of Entity2 |
development of Engineer B's report |
time:intervalDuring
http://www.w3.org/2006/time#intervalDuring |
At no time during the development of Engineer B's report did Engineer B talk to any representative o... [more] |
| 19 piles reaching driving refusal |
before
Entity1 is before Entity2 |
piles reaching predicted depth |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
his theories about why the 19 piles met driving refusal prior to predicted depth |
| test pile driving program |
meets
Entity1 ends exactly when Entity2 begins |
issuance of Engineer B's concluding report |
time:intervalMeets
http://www.w3.org/2006/time#intervalMeets |
At the conclusion of the program Engineer B reports that 19 piles do not meet the required factor of... [more] |
| issuance of Engineer B's report |
before
Entity1 is before Entity2 |
Engineer A's query of Engineer B |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
When queried by Engineer A after the report was issued by Engineer B |
| municipality's expert testimony |
before
Entity1 is before Entity2 |
Engineer B's report |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
the report appears to serve no purpose except to impugn Engineer A, or to support the original testi... [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.