Triple
T13940974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | If (Brothers in Rhythm House Mix) |
E335249
|
entity |
| Predicate | hasRemixStyle |
P83281
|
FINISHED |
| Object | club mix |
—
|
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: club mix | Statement: [If (Brothers in Rhythm House Mix), hasRemixStyle, club mix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRemixStyle Context triple: [If (Brothers in Rhythm House Mix), hasRemixStyle, club mix]
-
A.
hasRemix
Indicates that one creative work is a remix version derived from or based on another work.
-
B.
hasRemixType
chosen
Indicates that one creative work is a remix of another, specifying the particular type or style of remix relationship between them.
-
C.
hasRemixGenre
Indicates that a work or track has a remix version characterized by a particular musical genre.
-
D.
hasRemixed
Indicates that one entity has created a new version or adaptation of another entity by remixing it.
-
E.
hasRemixProducer
Indicates that one entity serves as the producer responsible for creating a remix version of another entity (typically a musical 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_69d81c6081b88190b53e317c3370c8fe |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2cf6e29881908ddb8efca9a456a3 |
completed | April 14, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69de05a3ccf88190b45c742db483fa08 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:17 p.m.