Triple
T28147694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiswas |
E714527
|
entity |
| Predicate | laterNetworkedAcross |
P193828
|
FINISHED |
| Object | ITV regions in the UK |
—
|
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: ITV regions in the UK | Statement: [Tiswas, laterNetworkedAcross, ITV regions in the UK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterNetworkedAcross Context triple: [Tiswas, laterNetworkedAcross, ITV regions in the UK]
-
A.
laterNetwork
Indicates that one network occurs or is established after another network in time.
-
B.
laterNetworkOfBroadcast
Indicates that one broadcast network succeeds or replaces another in time, coming into operation after the earlier network.
-
C.
continuedOnNetwork
Indicates that an entity (such as a show, series, or program) remained in production or broadcast on the same network beyond a given point in time.
-
D.
laterNetworkOfWork
Indicates that one work is created or occurs later in time than another work within the same network or sequence of related works.
-
E.
laterTransmission
Indicates that one transmission event occurs after another in time.
- F. None of above. chosen
Provenance (4 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_69efd6b033208190bf74f80a147e2092 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
| PDg | Predicate description generation | batch_69fd57b9cdec81908536c4159e375931 |
completed | May 8, 2026, 3:25 a.m. |
Created at: April 27, 2026, 9:57 p.m.