Triple
T23152950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tracey Fragments |
E578366
|
entity |
| Predicate | hasOnlineRemixProject |
P151126
|
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: [The Tracey Fragments, hasOnlineRemixProject, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnlineRemixProject Context triple: [The Tracey Fragments, hasOnlineRemixProject, yes]
-
A.
hasRemix
Indicates that one creative work is a remix version derived from or based on another work.
-
B.
hasRemixed
Indicates that one entity has created a new version or adaptation of another entity by remixing it.
-
C.
hasRemixProducer
Indicates that one entity serves as the producer responsible for creating a remix version of another entity (typically a musical work).
-
D.
hasRemixOrCovers
Indicates that one creative work is a remix or cover version of another work.
-
E.
hasRemixRelationshipWith
Indicates that one creative work is a remix, reworked version, or derived adaptation of another work.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18efaa1fc81908fb1987dbf732f46 |
completed | April 29, 2026, 4:54 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 4:01 p.m.