Triple
T32544493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Never Enough |
E831802
|
entity |
| Predicate | performedBy (on-screen actress) |
P135457
|
FINISHED |
| Object | Rebecca Ferguson |
—
|
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: Rebecca Ferguson | Statement: [Never Enough, performedBy (on-screen actress), Rebecca Ferguson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedBy (on-screen actress) Context triple: [Never Enough, performedBy (on-screen actress), Rebecca Ferguson]
-
A.
performedOnScreenBy
chosen
Indicates that an action, role, or performance is carried out by one entity in an on-screen context involving another entity.
-
B.
portrayedBy
Indicates that one entity serves as the actor or performer who represents or plays the role of another entity in a work or medium.
-
C.
performedForCharacterPortrayedBy
Indicates that an action or performance was carried out for the benefit of a fictional character as portrayed by a specific actor.
-
D.
playedBy
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
E.
performerCreditedAs
Indicates that a performer is associated with a work under a specific credited name or alias.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
Created at: May 1, 2026, 1:02 a.m.