Triple
T9923273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irving Berlin Music Corporation |
E187853
|
entity |
| Predicate | roleInMusicIndustry |
P68399
|
FINISHED |
| Object | copyright administration |
—
|
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: copyright administration | Statement: [Irving Berlin Music Corporation, roleInMusicIndustry, copyright administration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInMusicIndustry Context triple: [Irving Berlin Music Corporation, roleInMusicIndustry, copyright administration]
-
A.
musicIndustryRole
chosen
Indicates the professional function or position an entity holds within the music industry ecosystem.
-
B.
roleInArtistCareers
Indicates the specific function or contribution an entity has had in shaping, supporting, or influencing one or more artists’ professional careers.
-
C.
artistOccupation
Indicates the professional role or job that an artist holds or performs.
-
D.
roleInIndustry
Indicates the specific function, position, or capacity an entity holds within a particular industry or sector.
-
E.
musicalRole
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
- 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_69ca82b22a688190b52c75bd48429c10 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb59733188190900426e4e29ae5e3 |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:42 p.m.