Triple
T29097373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Playing Love |
E735043
|
entity |
| Predicate | notableComposerWork |
—
|
GENERATED |
| Object | true |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableComposerWork Context triple: [Playing Love, notableComposerWork, true]
-
A.
notableWorkComposedWith
Indicates that a notable work was created using, in collaboration with, or through the involvement of a particular tool, medium, system, or co-creative entity.
-
B.
notableComposition
chosen
Indicates that an entity is a significant or well-known work created by another entity, such as a notable musical, literary, or artistic composition.
-
C.
partOfComposerOeuvre
Indicates that a musical work belongs to and is included within the overall body of compositions created by a particular composer.
-
D.
notableArrangementByComposer
Indicates that a particular musical arrangement is especially recognized or significant and was created by the specified composer.
-
E.
notableComposerRole
Indicates that the subject has a significant or distinguished role as a composer in relation to the object.
- F. None of above.
Provenance (1 batch)
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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
Created at: April 28, 2026, 11:09 a.m.