Triple
T13069436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blues Babe Records |
E329414
|
entity |
| Predicate | primaryArtistType |
P20624
|
FINISHED |
| Object | R&B artists |
—
|
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: R&B artists | Statement: [Blues Babe Records, primaryArtistType, R&B artists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryArtistType Context triple: [Blues Babe Records, primaryArtistType, R&B artists]
-
A.
primaryArtist
Indicates that an entity is the main or lead artist responsible for a creative work, as opposed to supporting or contributing artists.
-
B.
primaryArtistNationality
Indicates the nationality associated with the main or primary artist involved in a work or context.
-
C.
performerType
chosen
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
-
D.
secondaryArtist
Indicates that an entity participates in a creative work as an additional or supporting artist, rather than as the primary artist.
-
E.
producerArtist
Indicates that one entity serves as the producer (e.g., overseeing or managing the creation) of a work created or performed by the artist 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d980ec8ba48190baf52c7823482680 |
completed | April 10, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9 p.m.