Triple
T13495166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SoundCloud rap |
E320735
|
entity |
| Predicate | gainedMainstreamAttention |
P71040
|
FINISHED |
| Object | mid 2010s |
—
|
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: mid 2010s | Statement: [SoundCloud rap, gainedMainstreamAttention, mid 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gainedMainstreamAttention Context triple: [SoundCloud rap, gainedMainstreamAttention, mid 2010s]
-
A.
helpedPropelToMainstreamFame
Indicates that one entity significantly contributed to another entity’s rise to widespread public recognition or mainstream popularity.
-
B.
gainedProminenceFor
Indicates that an entity became widely recognized or notable specifically because of another entity, action, or achievement.
-
C.
gainedRecognition
Indicates that an entity received acknowledgment, acclaim, or validation from others for its qualities, actions, or achievements.
-
D.
inceptionOfNotoriety
chosen
Indicates the point or event at which an entity first becomes widely known or gains significant public notoriety.
-
E.
wentViralOn
Indicates that content rapidly spread and gained widespread attention or popularity on a particular platform or medium.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf4da2c88190a867b53529d39545 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.