Triple
T15122527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | School Boy Records |
E361202
|
entity |
| Predicate | hasArtistManagementLink |
P117416
|
FINISHED |
| Object | SB Projects artist management division |
—
|
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: SB Projects artist management division | Statement: [School Boy Records, hasArtistManagementLink, SB Projects artist management division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtistManagementLink Context triple: [School Boy Records, hasArtistManagementLink, SB Projects artist management division]
-
A.
notableArtistManaged
Indicates that one notable artist is professionally managed or represented by another person or entity.
-
B.
linkedArtist
Indicates that there is an associated or related artist connected to the given entity.
-
C.
hasArtistRole
Indicates that an entity serves in the capacity or role of an artist in relation to another entity or context.
-
D.
associatedWithArtistGroup
Indicates that an entity has a relationship or connection with a particular artist group or collective.
-
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. 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0059f69a881909929a037a0eef702 |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:06 a.m.