Triple
T18482298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Show Stopper |
E451589
|
entity |
| Predicate | belongsToMusicGenreMovement |
P122163
|
FINISHED |
| Object | mid-2000s R&B |
—
|
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: mid-2000s R&B | Statement: [Show Stopper, belongsToMusicGenreMovement, mid-2000s R&B]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToMusicGenreMovement Context triple: [Show Stopper, belongsToMusicGenreMovement, mid-2000s R&B]
-
A.
hasGenreRelation
Indicates that there is an association between an entity and a specific genre, specifying the type or category it belongs to.
-
B.
belongsToWorkGenre
Indicates that a creative work is classified under or associated with a particular genre.
-
C.
associatedWithArtistMovement
chosen
Indicates that an entity has a connection or affiliation with a particular artistic movement or style.
-
D.
associatedWithGenreElement
Indicates that something has a connection or linkage to a specific genre-related element (such as a motif, convention, or stylistic feature).
-
E.
associatedArtistMovement
Indicates a relationship where an artist is linked to a particular artistic movement or style with which their work is identified.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e531d49a1881908cc2ad6132953c96 |
completed | April 19, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:35 a.m.