Triple
T28275187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10 Music Ltd |
E712968
|
entity |
| Predicate | handlesRoyaltiesFor |
P152016
|
FINISHED |
| Object | "Domino Dancing" |
—
|
NE NERFINISHED |
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: "Domino Dancing" | Statement: [10 Music Ltd, handlesRoyaltiesFor, "Domino Dancing"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesRoyaltiesFor Context triple: [10 Music Ltd, handlesRoyaltiesFor, "Domino Dancing"]
-
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.
royaltyRateOnProduction
Indicates the percentage or amount of royalty that must be paid based on the level or value of production.
-
C.
requiresRevenueSharingWith
chosen
Indicates that one party must share a portion of its revenue with another party as a condition of their relationship or agreement.
-
D.
allRoyaltiesDonatedTo
Indicates that all royalty earnings generated from a work or asset are given in full to a specified recipient or cause.
-
E.
tailorsCreditsFor
Indicates that one party customizes or adjusts credits to suit the needs, characteristics, or context of another party.
- 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_69efb52275788190ae5181ccebef18ce |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 11:19 p.m.