Triple
T29977319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tony Burrows |
E761483
|
entity |
| Predicate | leadVocalOnSong |
P9645
|
FINISHED |
| Object | Love Grows (Where My Rosemary Goes) |
—
|
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: Love Grows (Where My Rosemary Goes) | Statement: [Tony Burrows, leadVocalOnSong, Love Grows (Where My Rosemary Goes)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadVocalOnSong Context triple: [Tony Burrows, leadVocalOnSong, Love Grows (Where My Rosemary Goes)]
-
A.
leadPlaybackSinger
Indicates that one entity serves as the primary or main playback singer for another entity, such as a song or performance.
-
B.
coLeadVocalsBy
Indicates that the specified entity shares primary vocal duties on a performance or recording with one or more other lead vocalists.
-
C.
hasMaleLeadVocal
Indicates that the primary lead vocal in a performance, recording, or musical work is performed by a male singer.
-
D.
primaryVocalist
chosen
Indicates that the subject is the main singer or lead vocal performer for the object (such as a song, track, or musical work).
-
E.
leadSingleFeaturing
Indicates that an artist is featured on the lead single of another artist’s release.
- 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f678d69dc88190b0c31a769272f6d6 |
completed | May 2, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:33 p.m.