Triple
T16841092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BBC 7 |
E409411
|
entity |
| Predicate | succeededByBrandingChange |
P6643
|
FINISHED |
| Object | BBC Radio 4 Extra rebrand |
—
|
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: BBC Radio 4 Extra rebrand | Statement: [BBC 7, succeededByBrandingChange, BBC Radio 4 Extra rebrand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededByBrandingChange Context triple: [BBC 7, succeededByBrandingChange, BBC Radio 4 Extra rebrand]
-
A.
successorBranding
chosen
Indicates that one brand has replaced or continued another brand as its subsequent or updated identity.
-
B.
hasBranding
Indicates that one entity carries, displays, or is associated with the brand identity of another entity.
-
C.
brandingChangeDate
Indicates the date on which a change in branding (such as name, logo, or visual identity) took effect.
-
D.
logoChangedTo
Indicates that an entity’s logo has been updated or replaced with a new logo.
-
E.
announcedRebrandingAs
Indicates that one entity has publicly declared it will change its name, brand, or identity to that of another entity.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b3508ecc81909c0af299e07f4b31 |
completed | April 18, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.