Triple
T37501696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anthea Redfern |
E931978
|
entity |
| Predicate | coPresenterOf |
P5275
|
FINISHED |
| Object | The Generation Game |
—
|
NE NERFINISHED |
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: The Generation Game | Statement: [Anthea Redfern, coPresenterOf, The Generation Game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coPresenterOf Context triple: [Anthea Redfern, coPresenterOf, The Generation Game]
-
A.
coHostOf
chosen
Indicates a relationship where two or more entities jointly host the same event, program, or activity together.
-
B.
formerCoHostOf
Indicates that one entity previously served as a co-host together with another entity, but no longer holds that co-hosting role.
-
C.
coParticipantIn
Indicates that two or more entities take part together as participants in the same event, activity, or situation.
-
D.
originalCoHost
Indicates that an entity served as an initial or first co-host alongside another entity in a shared hosting role.
-
E.
coPresentedWithWorkBy
Indicates that a work is presented together with another specified work, typically within the same event, session, or exhibition.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.