Triple
T21721916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Last Night a DJ Saved My Life |
E536178
|
entity |
| Predicate | hasBeenCovered |
P91565
|
FINISHED |
| Object | by various artists |
—
|
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: by various artists | Statement: [Last Night a DJ Saved My Life, hasBeenCovered, by various artists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenCovered Context triple: [Last Night a DJ Saved My Life, hasBeenCovered, by various artists]
-
A.
hasBeenCoveredBy
chosen
Indicates that something has received coverage or treatment by another entity, such as being reported on, discussed, or addressed.
-
B.
hasCoveredEvent
Indicates that one entity has reported on, documented, or provided coverage of a particular event.
-
C.
hasCoverage
Indicates that one entity provides insurance or protection coverage for another entity or subject.
-
D.
previouslyCoveredBy
Indicates that something was earlier protected, enclosed, or overlaid by another object or material, but is no longer in that state.
-
E.
isCoveredIn
Indicates that one entity has its surface or area overlaid, coated, or blanketed by another substance or material.
- 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.