Triple
T36840850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PRS for Music |
E910403
|
entity |
| Predicate | collectsRoyaltiesFrom |
P195748
|
FINISHED |
| Object | radio stations |
—
|
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: radio stations | Statement: [PRS for Music, collectsRoyaltiesFrom, radio stations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectsRoyaltiesFrom Context triple: [PRS for Music, collectsRoyaltiesFrom, radio stations]
-
A.
associatedWithRoyalty
Indicates a relationship in which an entity has a notable connection to royalty, such as through lineage, service, patronage, or symbolic affiliation.
-
B.
allRoyaltiesDonatedTo
Indicates that all royalty earnings generated from a work or asset are given in full to a specified recipient or cause.
-
C.
royaltyRateOnProduction
Indicates the percentage or amount of royalty that must be paid based on the level or value of production.
-
D.
assetsDistributedTo
Indicates that assets are allocated, transferred, or paid out to a specified recipient or group of recipients.
-
E.
collects
Indicates that one entity gathers, accumulates, or brings together one or more other entities into its possession or control.
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
| PDg | Predicate description generation | batch_69fde49953c481909ac352ab36fa9ff2 |
completed | May 8, 2026, 1:26 p.m. |
Created at: May 3, 2026, 4:13 p.m.