Triple
T21455679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Step Into a World (Rapture's Delight) |
E529330
|
entity |
| Predicate | usesScratchDJ |
P124832
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Step Into a World (Rapture's Delight), usesScratchDJ, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesScratchDJ Context triple: [Step Into a World (Rapture's Delight), usesScratchDJ, yes]
-
A.
featuresDJScratching
chosen
Indicates that an audio track or performance includes DJ-style scratching as a prominent element.
-
B.
musicUsed
Indicates that one entity makes use of or incorporates another entity as music, such as in a performance, production, or media context.
-
C.
hasImprovisationFrom
Indicates that something includes or is derived from an improvisational performance or source.
-
D.
hasDrumProgrammingBy
Indicates that the drum programming for a work (such as a song or track) is created or performed by a specified entity.
-
E.
hasMainDJOrProducer
Indicates that an entity (such as a music show, event, or recording) has a specific person or group serving as its primary DJ or producer.
- 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9d6da3c819082a495f5434c5554 |
completed | April 23, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:08 p.m.