Triple
T17511885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Better Noise Music |
E426469
|
entity |
| Predicate | mediaActivities |
P41064
|
FINISHED |
| Object | music releases |
—
|
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: music releases | Statement: [Better Noise Music, mediaActivities, music releases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediaActivities Context triple: [Better Noise Music, mediaActivities, music releases]
-
A.
mediaActivity
chosen
Indicates an action or engagement involving the creation, use, sharing, or interaction with media content.
-
B.
mediaWork
Indicates a relationship where one entity is a media-related work (such as a film, book, recording, or other creative media production) associated with another entity.
-
C.
sharesActivity
Indicates that two or more entities participate in the same activity or engage in a common action or pastime.
-
D.
mediaMoment
Indicates a specific point or segment within a media item (such as a video, audio, or broadcast) where a notable event or action occurs.
-
E.
mediaExposure
Indicates the extent to which an entity is subjected to or receives attention from media channels such as television, radio, print, or online platforms.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4525c21c88190a9394c4bce006a38 |
completed | April 19, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.