Triple
T23597238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warner Music Nashville |
E582651
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | division of Warner Music Group |
C2019
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: division of Warner Music Group Context triple: [Warner Music Nashville, instanceOf, division of Warner Music Group]
-
A.
record label division
chosen
A record label division is a specialized branch within a larger music company that focuses on developing, marketing, and distributing music for a particular genre, market segment, or roster of artists.
-
B.
division of Warner Bros.
A division of Warner Bros. is a distinct organizational unit within the company responsible for specific entertainment functions such as film production, television, animation, or interactive media.
-
C.
record label conglomerate
A record label conglomerate is a large corporate entity that owns and manages multiple record labels, overseeing their operations, finances, and strategic direction within the music industry.
-
D.
division of Publicis Groupe
A division of Publicis Groupe is an organizational unit within the global communications and marketing holding company that focuses on a specific set of services, markets, or capabilities while operating under the broader Publicis corporate structure.
-
E.
division of The Walt Disney Company
A division of The Walt Disney Company is an organizational unit within the corporation responsible for managing a specific line of business, brand portfolio, or operational function under Disney’s overall corporate structure.
- F. None of above.
Provenance (1 batch)
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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:43 p.m.