Triple
T6954930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deepwater Horizon |
E161217
|
entity |
| Predicate | publicationDateOfSource |
P30105
|
FINISHED |
| Object | 2010 |
—
|
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 | Statement: [Deepwater Horizon, publicationDateOfSource, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicationDateOfSource Context triple: [Deepwater Horizon, publicationDateOfSource, 2010]
-
A.
finalPublicationDate
Indicates the date on which a work is officially and definitively published in its final form.
-
B.
publicationYear
Indicates the specific calendar year in which a work was formally published or released.
-
C.
publishedFor
Indicates that something (such as a work, document, or content) is published with a particular audience, recipient, or target group in mind.
-
D.
publicationPeriod
Indicates the span of time during which something is published, active in publication, or valid as a published work.
-
E.
hasPublicationDate
chosen
Indicates that an entity is associated with the specific date on which it was published.
- 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_69c68852a9a0819097797e31d492e273 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dace1a94819095311e4288f01784 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bf0a7c8190b5ed4aca22ba9b97 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:29 p.m.