Triple
T19200379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sam Cooke (1958 album) |
E470089
|
entity |
| Predicate | hasPerformerVocalRole |
P44280
|
FINISHED |
| Object | lead vocals by Sam Cooke |
—
|
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: lead vocals by Sam Cooke | Statement: [Sam Cooke (1958 album), hasPerformerVocalRole, lead vocals by Sam Cooke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformerVocalRole Context triple: [Sam Cooke (1958 album), hasPerformerVocalRole, lead vocals by Sam Cooke]
-
A.
musicalRole
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
-
B.
hasVocalPerformanceBy
chosen
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
-
C.
hasNotableVocalType
Indicates that an entity is associated with a specific, noteworthy type or quality of vocalization or voice.
-
D.
vocalistIn
Indicates that a person serves as a vocalist (singer) in a particular musical group, band, or ensemble.
-
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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f997879c8190ae7618d1ba0cede9 |
completed | April 20, 2026, 10:01 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bc158081908307dab01d9478c6 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:07 p.m.