Triple
T6608658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newsround |
E149181
|
entity |
| Predicate | broadcastScheduleChange |
P72420
|
FINISHED |
| Object | moved primarily to CBBC channel in 2013 |
—
|
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: moved primarily to CBBC channel in 2013 | Statement: [Newsround, broadcastScheduleChange, moved primarily to CBBC channel in 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastScheduleChange Context triple: [Newsround, broadcastScheduleChange, moved primarily to CBBC channel in 2013]
-
A.
broadcastProgram
Indicates that a media outlet or channel transmits a specific program to an audience via a broadcast medium.
-
B.
broadcastTimeSlot
Indicates the specific time period during which a broadcast (such as a TV or radio program) is scheduled to air.
-
C.
broadcastDuring
Indicates that one event or program is broadcast while another specified time period or event is occurring.
-
D.
broadcastBlock
Indicates that one entity transmits or disseminates a block (such as a data block or message) to multiple recipients or across a network.
-
E.
broadcastBegan
Indicates that the transmission or airing of a broadcast has started.
- 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_69c687ebc680819094caf71faba2efe2 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cf3796d08190a26e988386089447 |
completed | March 27, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69c6acfed25481909cac74c84a9fe088 |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6cf3683d08190b19e2aad30f2800f |
completed | March 27, 2026, 6:40 p.m. |
Created at: March 27, 2026, 1:57 p.m.