Triple
T31537995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brownstone Records |
E804661
|
entity |
| Predicate | hasCollaboratorOfArtist |
P110830
|
FINISHED |
| Object | James Brown collaborator Bobby Byrd |
—
|
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: James Brown collaborator Bobby Byrd | Statement: [Brownstone Records, hasCollaboratorOfArtist, James Brown collaborator Bobby Byrd]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollaboratorOfArtist Context triple: [Brownstone Records, hasCollaboratorOfArtist, James Brown collaborator Bobby Byrd]
-
A.
hasArtistSiblingCollaboration
Indicates that two artist siblings have worked together on a shared artistic project or collaboration.
-
B.
musicalCollaborator
chosen
Indicates a relationship where two or more entities work together in creating, performing, or producing music.
-
C.
hasArtistRole
Indicates that an entity serves in the capacity or role of an artist in relation to another entity or context.
-
D.
belongsToArtist
Indicates that something is owned, created, or otherwise associated with a specific artist.
-
E.
hasArtist
Indicates that an entity (such as a work or item) is associated with or created by a specific artist.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a02f10505988190be5fd57566a90e0f |
completed | May 12, 2026, 9:21 a.m. |
| PD | Predicate disambiguation | batch_6a02f03a8c1481909e137e270119f7ef |
completed | May 12, 2026, 9:17 a.m. |
Created at: April 30, 2026, 10:04 p.m.