Triple
T1445229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oil Pollution Act of 1990 |
E31161
|
entity |
| Predicate | enactedAfterEvent |
P6514
|
FINISHED |
| Object | Exxon Valdez oil spill |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Exxon Valdez oil spill | Statement: [Oil Pollution Act of 1990, enactedAfterEvent, Exxon Valdez oil spill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enactedAfterEvent Context triple: [Oil Pollution Act of 1990, enactedAfterEvent, Exxon Valdez oil spill]
-
A.
enactedAfter
chosen
Indicates that one enactment event occurred later in time than another enactment event.
-
B.
createdAfterEvent
Indicates that the creation of one entity occurred after a specified event in time.
-
C.
enactedDuring
Indicates that an action, event, or state occurred within the temporal span of a specified time period or event.
-
D.
heldAfter
Indicates that one event or state occurs or is maintained at some point in time after another specified event or state.
-
E.
tookPlaceAfter
Indicates that one event or occurrence happened later in time than another event or occurrence.
- F. None of above.
Provenance (3 batches)
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_69a4991633388190a4d61b5a98aa407a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c55714588190a95b4f677c21cbaa |
completed | March 1, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69a4c47a840c819083307a65c027a19e |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.