Triple
T9614252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSD |
E232178
|
entity |
| Predicate | becameMainstream |
P2352
|
FINISHED |
| Object | 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: 2010s | Statement: [SSD, becameMainstream, 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameMainstream Context triple: [SSD, becameMainstream, 2010s]
-
A.
helpedPropelToMainstreamFame
Indicates that one entity significantly contributed to another entity’s rise to widespread public recognition or mainstream popularity.
-
B.
popularizedAfter
Indicates that one entity became widely known, accepted, or influential only after another specified entity had already gained popularity.
-
C.
gainedProminenceFor
Indicates that an entity became widely recognized or notable specifically because of another entity, action, or achievement.
-
D.
popularizedIn
chosen
Indicates that something became widely known, accepted, or fashionable within a particular place, time period, or context.
-
E.
becameStandardFor
Indicates that something was adopted and established as the usual or accepted norm for a particular purpose, context, or group.
- 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_69ca84867bb88190b4b57dd5a56d5691 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9aaaa47881908d69381d4d11f49b |
completed | April 1, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a6fd2481908efd131e207b8143 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:09 p.m.