Triple
T33339681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Someone to Love Me (Naked) |
E853634
|
entity |
| Predicate | hasRemixOrVersionOf |
—
|
GENERATED |
| Object | Someone to Love Me |
—
|
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: hasRemixOrVersionOf Context triple: [Someone to Love Me (Naked), hasRemixOrVersionOf, Someone to Love Me]
-
A.
hasRemixOrAlternateVersions
Indicates that an original work has one or more remix, alternate, or variant versions derived from it.
-
B.
hasRemixOrCovers
Indicates that one creative work is a remix or cover version of another work.
-
C.
hasRemixRelationshipWith
Indicates that one creative work is a remix, reworked version, or derived adaptation of another work.
-
D.
hasRemixOrEdit
Indicates that one work is a remix or edited version of another work, or that such a derivative relationship exists between two works.
-
E.
hasRemix
chosen
Indicates that one creative work is a remix version derived from or based on another work.
- 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:34 a.m.