Triple
T3371860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBBC |
E70972
|
entity |
| Predicate | typicalBroadcastHours |
P6833
|
FINISHED |
| Object | daytime and early evening |
—
|
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: daytime and early evening | Statement: [CBBC, typicalBroadcastHours, daytime and early evening]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBroadcastHours Context triple: [CBBC, typicalBroadcastHours, daytime and early evening]
-
A.
typicalBroadcastFormat
Indicates the usual or standard broadcast format in which something (such as a program or content) is typically transmitted.
-
B.
broadcastNetworkTypical
Indicates that a given broadcast network is the one typically or commonly associated with airing the specified content or program.
-
C.
broadcastDay
Indicates the specific day on which a program, event, or content is broadcast or scheduled to be broadcast.
-
D.
broadcastTimeSlot
Indicates the specific time period during which a broadcast (such as a TV or radio program) is scheduled to air.
-
E.
typicalTimes
chosen
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
- 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_69ad85a729d48190afd789cd8417f289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2bc9bc881908b22edd631a1c110 |
completed | March 8, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69ada433059881908e46f38cc5f40a32 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.