Triple
T31241005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weapon of Choice (Fatboy Slim music video) |
E796559
|
entity |
| Predicate | vocalistOnSong |
P160279
|
FINISHED |
| Object | Bootsy Collins |
—
|
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: Bootsy Collins | Statement: [Weapon of Choice (Fatboy Slim music video), vocalistOnSong, Bootsy Collins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalistOnSong Context triple: [Weapon of Choice (Fatboy Slim music video), vocalistOnSong, Bootsy Collins]
-
A.
vocalistIn
Indicates that a person serves as a vocalist (singer) in a particular musical group, band, or ensemble.
-
B.
vocalistOnOriginalRecording
chosen
Indicates that the subject served as the vocalist on the original recording of the work or track.
-
C.
hasVerseVocalist
Indicates that a person performs the vocal part specifically in the verse section of a musical work or recording.
-
D.
composerOfVocalVersion
Indicates that one entity is the composer who created a vocal (sung or voice-based) version of a work associated with another entity.
-
E.
usesLeadVocalsFrom
Indicates that one musical work incorporates or is built around the lead vocal track taken from another work.
- 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_69f224db69ac81909a370adad6a7ac7c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 29, 2026, 9:11 p.m.