Triple
T33293238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love Ballad |
E852370
|
entity |
| Predicate | leadVocalistOnOriginalVersion |
P160279
|
FINISHED |
| Object | Jeffrey Osborne |
—
|
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: Jeffrey Osborne | Statement: [Love Ballad, leadVocalistOnOriginalVersion, Jeffrey Osborne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadVocalistOnOriginalVersion Context triple: [Love Ballad, leadVocalistOnOriginalVersion, Jeffrey Osborne]
-
A.
vocalistOnOriginalRecording
chosen
Indicates that the subject served as the vocalist on the original recording of the work or track.
-
B.
usesOriginalVocalsFrom
Indicates that one work incorporates the original, unaltered vocal recordings from another work.
-
C.
leadVocalistOnNotableVersion
Indicates that a person served as the lead vocalist on a specific notable version or recording of a work.
-
D.
originallyIntendedVocalist
Indicates that a person was the first or planned singer for a musical work or performance, even if they did not ultimately perform it.
-
E.
composerOfVocalVersion
Indicates that one entity is the composer who created a vocal (sung or voice-based) version of a work associated with another entity.
- 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:33 a.m.