Triple
T16835911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hal Leonard Corporation |
E409276
|
entity |
| Predicate | roleInBooseyAndHawkesCatalog |
P114690
|
FINISHED |
| Object | print distributor |
—
|
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: print distributor | Statement: [Hal Leonard Corporation, roleInBooseyAndHawkesCatalog, print distributor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInBooseyAndHawkesCatalog Context triple: [Hal Leonard Corporation, roleInBooseyAndHawkesCatalog, print distributor]
-
A.
recordLabelCatalogRole
chosen
Indicates the role an entity plays in relation to a record label’s catalog, such as managing, distributing, or curating its releases.
-
B.
musicIndustryRole
Indicates the professional function or position an entity holds within the music industry ecosystem.
-
C.
artistOccupation
Indicates the professional role or job that an artist holds or performs.
-
D.
recordLabelArtist
Indicates that a musical artist is signed to, represented by, or releases recordings through a particular record label.
-
E.
hasMusicalWorkType
Indicates that a musical work is associated with a specific type or category of musical composition.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b34d49d08190aa62f05d67244584 |
completed | April 18, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.