Triple
T30712104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terry Ellis |
E781922
|
entity |
| Predicate | roleInMusicBusiness |
P68399
|
FINISHED |
| Object | label founder |
—
|
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: label founder | Statement: [Terry Ellis, roleInMusicBusiness, label founder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInMusicBusiness Context triple: [Terry Ellis, roleInMusicBusiness, label founder]
-
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.
musicSceneRole
Indicates the specific function or position an entity holds within a particular music scene or musical community.
-
D.
occupationInMusical
Indicates that an entity holds a specific occupation or role within the context of a musical work or production.
-
E.
employedMusician
Indicates that a musician is employed, typically by an organization, venue, or individual, to perform musical work.
- 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff7c96e6dc8190b89554480ebcea39 |
completed | May 9, 2026, 6:27 p.m. |
| PD | Predicate disambiguation | batch_69ff7c2381748190ad9a2176e0e478cd |
completed | May 9, 2026, 6:25 p.m. |
Created at: April 29, 2026, 8:35 p.m.