Triple
T16841137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BBC Radio 7 |
E409412
|
entity |
| Predicate | hasArchiveContent |
P53043
|
FINISHED |
| Object | classic BBC comedy series |
—
|
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: classic BBC comedy series | Statement: [BBC Radio 7, hasArchiveContent, classic BBC comedy series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchiveContent Context triple: [BBC Radio 7, hasArchiveContent, classic BBC comedy series]
-
A.
hasTarContent
Indicates that something contains or is characterized by a certain amount or presence of tar.
-
B.
archiveContent
chosen
Indicates that content is being stored or moved into an archive state for long-term retention or historical reference.
-
C.
hasNotableArchive
Indicates that an entity maintains or is associated with an archive that is considered significant or noteworthy.
-
D.
archiveAvailability
Indicates whether something is stored or accessible in an archive, and under what conditions it can be retrieved.
-
E.
hasContentFrom
Indicates that one entity’s content is derived from, includes, or is based on 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.