Triple
T11019541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FilmStruck |
E260448
|
entity |
| Predicate | shutdownYear |
P19867
|
FINISHED |
| Object | 2018 |
—
|
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 | Statement: [FilmStruck, shutdownYear, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shutdownYear Context triple: [FilmStruck, shutdownYear, 2018]
-
A.
closureYear
chosen
Indicates the year in which an entity (such as an organization, facility, or service) ceased operations or was officially closed.
-
B.
exitYear
Indicates the year in which an entity leaves, finishes, or ceases its association with another entity or context.
-
C.
discontinuationAnnouncementYear
Indicates the year in which the discontinuation of something (such as a product, service, or program) was officially announced.
-
D.
shutdownPeriod
Indicates a time interval during which a system, service, or process is intentionally turned off or not operational.
-
E.
shutdownCapability
Indicates the ability or permission for one entity to power off, deactivate, or terminate the operation of another entity or system.
- 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.