Triple
T31900272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lido Shuffle |
E814400
|
entity |
| Predicate | hasNotableBackingVocalist |
P202878
|
FINISHED |
| Object | Augie Johnson |
—
|
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: Augie Johnson | Statement: [Lido Shuffle, hasNotableBackingVocalist, Augie Johnson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableBackingVocalist Context triple: [Lido Shuffle, hasNotableBackingVocalist, Augie Johnson]
-
A.
hasBackingVocals
Indicates that one musical performance, track, or part includes supporting vocal contributions accompanying a primary vocal line.
-
B.
hasOutroVocalist
Indicates that an entity (such as a song or track) features a vocalist specifically during its outro section.
-
C.
hasNotableVocalType
Indicates that an entity is associated with a specific, noteworthy type or quality of vocalization or voice.
-
D.
hasBackwardVocals
Indicates that the subject uses or contains backward (reversed) vocal audio in relation to the object.
-
E.
hasVerseVocalist
Indicates that a person performs the vocal part specifically in the verse section of a musical work or recording.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00ca5e907481909d391afd55938a1b |
completed | May 10, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_6a00ca2214348190a674a85ede709e2e |
completed | May 10, 2026, 6:10 p.m. |
| PDg | Predicate description generation | batch_6a00ca5de6748190bc67a1fd9f3d0b3a |
completed | May 10, 2026, 6:11 p.m. |
Created at: April 30, 2026, 11:59 p.m.