Triple
T24657974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soul Revolution |
E610446
|
entity |
| Predicate | hasRemixOrDubVersion |
P9639
|
FINISHED |
| Object | Soul Revolution Part II (dub version) |
—
|
NE NERFINISHED |
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: Soul Revolution Part II (dub version) | Statement: [Soul Revolution, hasRemixOrDubVersion, Soul Revolution Part II (dub version)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRemixOrDubVersion Context triple: [Soul Revolution, hasRemixOrDubVersion, Soul Revolution Part II (dub version)]
-
A.
hasRemixOrCovers
Indicates that one creative work is a remix or cover version of another work.
-
B.
hasRemixed
Indicates that one entity has created a new version or adaptation of another entity by remixing it.
-
C.
hasRemix
chosen
Indicates that one creative work is a remix version derived from or based on another work.
-
D.
hasRemixVariant
Indicates that one entity is a remix version or reworked variant of another entity.
-
E.
hasCoverVersions
Indicates that a musical work has one or more recorded versions performed or produced by artists other than the original creator.
- 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:34 a.m.