Triple
T16879212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bring the Noise |
E421373
|
entity |
| Predicate | collaborationVersionReleaseYear |
P124825
|
FINISHED |
| Object | 1991 |
—
|
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: 1991 | Statement: [Bring the Noise, collaborationVersionReleaseYear, 1991]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaborationVersionReleaseYear Context triple: [Bring the Noise, collaborationVersionReleaseYear, 1991]
-
A.
keyWorkReleaseYear
Indicates the year in which a key work (such as a major publication, artwork, or product) was first released.
-
B.
bestKnownVersionReleaseYear
Indicates the calendar year in which the most widely recognized or prominent version of something was released.
-
C.
ARVersionAnnouncementYear
Indicates the year in which a specific version of an augmented reality (AR) product or system was officially announced.
-
D.
coverVersionReleaseYear
Indicates the year in which a particular cover version of an original work was released.
-
E.
inspiredWorkReleaseYear
Indicates the year in which a work that served as inspiration for another work was released.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3b7f9aea0819090aef3c0c1ad349d |
completed | April 18, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e32e2c07b081908c8fee9f5507bb9e |
completed | April 18, 2026, 7:09 a.m. |
Created at: April 10, 2026, 5:29 a.m.