Triple
T13143007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tampa Bay Storm |
E312257
|
entity |
| Predicate | announcedCeasingOperations |
P42352
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Tampa Bay Storm, announcedCeasingOperations, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedCeasingOperations Context triple: [Tampa Bay Storm, announcedCeasingOperations, 2017]
-
A.
announcedPermanentClosure
Indicates that an entity has formally stated that it will cease operations or availability indefinitely and not reopen.
-
B.
discontinuationAnnouncedBy
Indicates that an entity’s discontinuation (e.g., of a product, service, or activity) has been formally announced by a specific agent or organization.
-
C.
decommissioningEndDate
Indicates the date on which a decommissioning process or status for something is completed or officially ends.
-
D.
discontinuationAnnouncementDate
chosen
Indicates the date on which an official announcement is made that something (such as a product, service, or feature) will be discontinued.
-
E.
cessationDate
Indicates the date on which an ongoing state, activity, or relationship comes to an end.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d981d24da48190b99e713878e8d003 |
completed | April 10, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69d9804543cc8190a23cd7da59a12a7b |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:10 p.m.