Triple
T11019571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FilmStruck |
E260448
|
entity |
| Predicate | announcedShutdownDate |
P42352
|
FINISHED |
| Object | 2018-10-26 |
—
|
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: 2018-10-26 | Statement: [FilmStruck, announcedShutdownDate, 2018-10-26]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedShutdownDate Context triple: [FilmStruck, announcedShutdownDate, 2018-10-26]
-
A.
finalShutdownDate
Indicates the date on which an entity is permanently shut down or ceases operation.
-
B.
discontinuationAnnouncementDate
chosen
Indicates the date on which an official announcement is made that something (such as a product, service, or feature) will be discontinued.
-
C.
decommissioningStartDate
Indicates the date on which the process of taking an asset or system out of active service is initiated.
-
D.
decommissioningEndDate
Indicates the date on which a decommissioning process or status for something is completed or officially ends.
-
E.
cancellationAnnouncedOn
Indicates that the cancellation of something (e.g., an event, service, or agreement) was publicly announced on a specific date or time.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797a9e8788190a0f45b52bad1bfb5 |
completed | April 9, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69d72e995e008190bbffb314129ed0cd |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.