Triple
T3440128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITV Digital |
E72543
|
entity |
| Predicate | serviceClosure |
P42074
|
FINISHED |
| Object | all pay TV services ceased in 2002 |
—
|
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: all pay TV services ceased in 2002 | Statement: [ITV Digital, serviceClosure, all pay TV services ceased in 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceClosure Context triple: [ITV Digital, serviceClosure, all pay TV services ceased in 2002]
-
A.
closureReason
Indicates the reason or cause for which an entity, process, or case has been closed or terminated.
-
B.
closureProcess
Indicates the procedure or set of actions carried out to formally conclude, finalize, or terminate an ongoing activity, case, or process.
-
C.
serviceRetirement
chosen
Indicates that an entity ends or withdraws a service, marking it as no longer available or in active use.
-
D.
closureProgram
Indicates that an entity is a program or plan specifically associated with the closure or shutdown of another entity or operation.
-
E.
originalServiceEnded
Indicates that a previously existing or initial service has come to an end or has been terminated.
- 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_69ad85af50288190a854b76653deee6f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9f833e88190b5e813f115621a5f |
completed | March 8, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69adae00ad588190bef24373b58a2e1a |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.