Triple
T2861457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deepwater Horizon oil spill |
E63331
|
entity |
| Predicate | leakStoppedDate |
P22869
|
FINISHED |
| Object | 2010-07-15 |
—
|
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: 2010-07-15 | Statement: [Deepwater Horizon oil spill, leakStoppedDate, 2010-07-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leakStoppedDate Context triple: [Deepwater Horizon oil spill, leakStoppedDate, 2010-07-15]
-
A.
leakDate
Indicates the date on which something (such as information, content, or a product) became publicly known or was unofficially released.
-
B.
suspensionDate
Indicates the date on which an entity’s normal status, operation, or privileges are formally suspended.
-
C.
stoppedAt
chosen
Indicates that an entity has come to a halt or pause at a specific location or point in time.
-
D.
immediateCauseDate
Indicates the specific date on which an event or condition directly caused another event or outcome to occur.
-
E.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active use.
- 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_69ab4c41e8c08190a9e8f5249cc12610 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf8df8288190816767169ea7cbf9 |
completed | March 7, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69abdd123ec48190af50a1859aea50b7 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.