Triple
T9372819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Call Me Back Again |
E225571
|
entity |
| Predicate | performerRole_Linda McCartney |
P88209
|
FINISHED |
| Object | backing vocals |
—
|
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: backing vocals | Statement: [Call Me Back Again, performerRole_Linda McCartney, backing vocals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performerRole_Linda McCartney Context triple: [Call Me Back Again, performerRole_Linda McCartney, backing vocals]
-
A.
producerDuoMember
Indicates that one entity is a member of a producer duo that is represented by the other entity.
-
B.
performerCreditedAs
Indicates that a performer is associated with a work under a specific credited name or alias.
-
C.
notableBandMember
Indicates that the subject is a member of the band in the object and is recognized as particularly prominent or significant within that band.
-
D.
isFrontmanOf
Indicates that a person serves as the lead singer or primary representative performer of a band or musical group.
-
E.
performerBirthName
Indicates the full name a performer was given at birth, as distinct from any stage or professional name they may use.
- F. None of above. chosen
Provenance (4 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_69ca842cbddc819099d71ecec48cf9e5 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50852a388190be936df1382216bc |
completed | April 1, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69cc7a6abb8c81908c7a2f4ee92cc949 |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc955a38108190b602d1e73725f11b |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:43 p.m.