Triple
T21721915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Last Night a DJ Saved My Life |
E536178
|
entity |
| Predicate | hasBeenRemixed |
P67559
|
FINISHED |
| Object | multiple times by various producers |
—
|
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: multiple times by various producers | Statement: [Last Night a DJ Saved My Life, hasBeenRemixed, multiple times by various producers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenRemixed Context triple: [Last Night a DJ Saved My Life, hasBeenRemixed, multiple times by various producers]
-
A.
hasRemixed
Indicates that one entity has created a new version or adaptation of another entity by remixing it.
-
B.
hasRemix
Indicates that one creative work is a remix version derived from or based on another work.
-
C.
hasRemixProducer
chosen
Indicates that one entity serves as the producer responsible for creating a remix version of another entity (typically a musical work).
-
D.
hasRemixRelationshipWith
Indicates that one creative work is a remix, reworked version, or derived adaptation of another work.
-
E.
isRemixWith
Indicates that one creative work is a remix created in collaboration with, or incorporating elements from, another specific 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd97032c08190820b87a288e77293 |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:47 p.m.