Triple
T5514018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armchair Theatre |
E144636
|
entity |
| Predicate | inPublication |
P309
|
FINISHED |
| Object | Radio Times listings |
—
|
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: Radio Times listings | Statement: [Armchair Theatre, inPublication, Radio Times listings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inPublication Context triple: [Armchair Theatre, inPublication, Radio Times listings]
-
A.
publishedIn
chosen
Indicates that a work (such as an article, paper, or book) has been formally released or made available within a specific venue, medium, or publication.
-
B.
involvesPublication
Indicates that an action, event, or process includes or is associated with a specific publication as a relevant component.
-
C.
publicationType
Indicates the specific category or format of a published work that characterizes how it is issued or presented.
-
D.
publicationAbout
Indicates that a publication has content whose subject or focus is the referenced entity.
-
E.
publicationBody
Indicates the organization or entity that serves as the publishing body responsible for issuing the referenced work.
- 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_69c008f77ff88190b0cd50ca207295d1 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f5b4e988190b590b4157cf089c1 |
completed | March 22, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69c01b07bde08190b3933b96bdc70dd5 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:33 p.m.