Triple
T27691200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paranoimia (Extended Version) |
E698161
|
entity |
| Predicate | isRemixReleaseTypicalOf |
P162952
|
FINISHED |
| Object | 1980s 12-inch culture |
—
|
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: 1980s 12-inch culture | Statement: [Paranoimia (Extended Version), isRemixReleaseTypicalOf, 1980s 12-inch culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRemixReleaseTypicalOf Context triple: [Paranoimia (Extended Version), isRemixReleaseTypicalOf, 1980s 12-inch culture]
-
A.
isRemixWith
Indicates that one creative work is a remix created in collaboration with, or incorporating elements from, another specific work.
-
B.
hasRemix
Indicates that one creative work is a remix version derived from or based on another work.
-
C.
hasRemixVariant
Indicates that one entity is a remix version or reworked variant of another entity.
-
D.
hasRemixRelationshipWith
Indicates that one creative work is a remix, reworked version, or derived adaptation of another work.
-
E.
hasRemixed
Indicates that one entity has created a new version or adaptation of another entity by remixing it.
- F. None of above. chosen
Provenance (4 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63577d4548190b072b84c0a48de74 |
completed | May 2, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f6305219f08190b55f6193a4a49984 |
completed | May 2, 2026, 5:11 p.m. |
Created at: April 27, 2026, 2:52 p.m.