Triple
T13101380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1969 Santa Barbara oil spill |
E310726
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | offshore drilling accident |
C8362
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: offshore drilling accident Context triple: [1969 Santa Barbara oil spill, instanceOf, offshore drilling accident]
-
A.
maritime incident
chosen
A maritime incident is any unexpected or unintended event involving a vessel or marine operation that compromises or threatens safety, the environment, property, or normal navigation at sea or in navigable waters.
-
B.
industrial accident
An industrial accident is an unplanned event occurring in a workplace or industrial setting that results in injury, illness, damage, or disruption to people, equipment, or the environment.
-
C.
offshore oil and gas development project
An offshore oil and gas development project is a large-scale, capital-intensive initiative that plans, designs, constructs, and operates facilities at sea to extract, process, and transport hydrocarbons from subsea reservoirs to market.
-
D.
offshore drilling contractor
An offshore drilling contractor is a specialized company that owns and operates offshore drilling rigs and related equipment to explore for and extract oil and gas beneath the seabed on behalf of energy producers.
-
E.
hazardous offshore area
A hazardous offshore area is a marine zone beyond the shoreline that poses significant risks to navigation, operations, or safety due to natural or man-made dangers such as rough seas, strong currents, submerged obstacles, or industrial activities.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:04 p.m.