Patent Publication Number: US-9406072-B2

Title: Demographic and media preference prediction using media content data analysis

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This application is a continuation-in-part of U.S. application Ser. No. 13/849,167, filed Mar. 22, 2013, which claims priority to U.S. Provisional Application No. 61/617,553, filed Mar. 29, 2012; this application also claims priority to U.S. Provisional Application No. 61/798,827, filed Mar. 15, 2013; and the contents of the mentioned prior applications are hereby incorporated by reference as if fully stated herein. 
    
    
     BACKGROUND 
     I. Field 
     Example aspects of the present invention generally relate to predicting demographics and/or taste preferences from music or other media data. 
     II. Related Art 
     In business communications, it is useful to direct communications to specific groups of recipients. For example, an advertiser may wish to direct targeted advertisements to customers whose demographics (male, elderly, etc.) indicate that they are more receptive to such advertisements. To that end, it is helpful to identify demographics of customers or other recipients from available source data. 
     However, existing approaches tend to rely on a relatively small set of source data, such as a web browsing history. Such approaches generally lead to predictions which have less accuracy than desired. 
     BRIEF DESCRIPTION 
     The example embodiments described herein address the above-identified needs by providing methods, systems and computer program products for predicting data. A name or title is obtained from a taste profile. There is an index into a data set based on the name or title, and a set of terms and corresponding term weights associated with the name or title are retrieved. A sparse vector is constructed based on the set of terms and term weights. The sparse vector is input to a training model including target data. The target data includes a subset of test data which has a correspondence to a predetermined target metric of data (e.g., demographic data). A respective binary value and confidence level is output for each term, corresponding to an association between the term and the target metric. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       The features and advantages of the example embodiments of the invention presented herein will become more apparent from the detailed description set forth below when taken in conjunction with the following drawings. 
         FIG. 1  is a representative view of a system in which some embodiments of the invention may be implemented. 
         FIG. 2  illustrates a representative view of a set of musical data for an artist according to an example embodiment. 
         FIG. 3  illustrates a representative view of a taste profile according to an example embodiment. 
         FIG. 4  depicts a representative view of inverted indices for terms associated with musical data according to an example embodiment. 
         FIG. 5  is a flowchart diagram showing an exemplary procedure for predicting demographic data. 
         FIGS. 6A-6G  are representative views of results from predicting demographic data according to example embodiments. 
         FIG. 7  is a block diagram of a device for use with various example embodiments of the invention. 
     
    
    
     DETAILED DESCRIPTION 
     The example embodiments of the invention presented herein are directed to methods, systems and computer program products for predicting demographic data. This description is not intended to limit the application of the example embodiments presented herein. In fact, after reading the following description, it will be apparent to one skilled in the relevant art(s) how to implement the following example embodiments in alternative embodiments, such as such as a services-based environment, a web media-based environment, etc. 
       FIG. 1  illustrates a representative view of a system in which some embodiments of the invention may be implemented. The environment comprises several modules, which may be embodied as, for example, computer hardware elements executing software, as described below with respect to  FIG. 7 . 
     As shown in  FIG. 1 , the system includes management modules  101 , which control processing including taste profile analysis. In response to a query, management modules  101  retrieve terms and weights associated with an artist, song title, or other preference of a user, and use the terms and weights to predict demographic data or other taste preferences, as described more fully below. 
     Taste profiles  103  contains records indicating the music taste (or other tastes) of users. In one example embodiment, each taste profile is a representation of musical activity, and may include a wide range of information such as artist plays, song plays, skips, dates of listen by the user, songs per day, playlists, play counts, start/stop/skip data for portions of a song or album, contents of collections, user rankings, preferences, or other mentions received via a client device, or other media plays, such as websites visited, book titles, movies watched, playing activity during a movie or other presentations, ratings, or terms corresponding to the media, such as “comedy”, “sexy”, etc. Further details of the taste profile are described below with respect to  FIG. 3 . 
     Data source  105  contains records as inverted indices in which terms are indexes to documents for artist names or song titles. For example, the terms “Sexy”, “R&amp;B”, and “Dance” might index to a document for artist “Beyonce”, as described more fully below with respect to  FIG. 4 . Of course, records can be implemented in any other way that allows fast retrieval of desired information. 
     Data source  107  is a data set which contains (1) documents over various domains, such as artists and titles, and (2) terms and weights associated with each artist and/or each title.  FIG. 2  illustrates an example document  201  according to such a data set. The document  201  contains a document ID  203  which uniquely identifies the document. In one embodiment, the domain concerns musical artists. In accordance with such a domain, document  201  contains an artist ID  205 , an artist name  207 , and a list of descriptions  209  related to a subject of the domain under consideration, in this case the artist. Each description is a term-weight pair, where the term describes the subject and the weight indicates how closely the term describes the subject. Data source  107  may store a wide range of terms associated with each artist name or song title, and may be updated at regular intervals, e.g., once per week or month. 
     For example, one example embodiment might include a data set including over 10,000 terms for each artist from various sources of data about music (or other media such as books, movies or games), along with associated weights. The terms may be weighted based on how important, how often mentioned or how closely related the term is to the artist. The terms may contain information about location, genre, style, marketing classifications, sales predictions, reviews, chat room dialogue transcriptions, biographies, recent news articles, time-dependent popularity and familiarity data, cultural analysis data, and the like. For example, the artist “Beyonce” might be associated with a vector of terms including “R&amp;B”, “sexy”, “dance”, etc., with corresponding weights of 0.8, 0.6 and 0.5. In another example, “Aphex Twin” might be represented not by a single entity, but rather by a vector of terms with probabilities, e.g., [“idm”:0.9, “glitch”:0.5, “hardcore”:0.2], etc. Additional information regarding generation of terms and weights can be found in U.S. Pat. No. 7,772,478, entitled “Understanding Music”, the contents of which are incorporated by reference herein. By utilizing a larger amount of data associated with the artist or song names, it is possible to predict demographics and/or taste preferences more accurately than just using a single attribute such as the song title alone. Put another way, the usage of a song, artist, movie, etc. in a taste profile to determine predictive qualities can be enhanced by expanding these media items into descriptive terms and using those terms as the inputs to the predictive model. 
     API  109  is an application programming interface used to communicate with a client device to receive or transmit information. For example, API  109  receives a query seeking a prediction of demographic data, and returns a query result. To that end, API  109  may perform user authentication or other user-related activities. In addition, API  109  may present a user interface to a client device or interact with a client device to receive input and display output. 
     User database  111  contains records having identification information of users. In this example, “user” may correspond to a customer such as an advertising entity who submits a query via a client device regarding which demographics are associated with particular musical tastes. On the other hand, “user” may also correspond to a person or group whose musical tastes are being examined, as described more fully below. In either case, a user may or may not be required to register and/or input other data to the database. 
       FIG. 3  illustrates an entry in taste profiles  103 , which contains records indicating user musical (or other) tastes. In one example embodiment, a taste profile is a representation of musical activity, and includes a wide range of information such as artist plays, song plays, skips, ratings by the user, date of listen by the user, songs per day, playlists, play counts, start/stop/skip data for portions of a song or album, contents of collections, user rankings, preferences, or mentions, etc. Thus, the taste profile data includes, in addition to an artist name or a song title, one or more of the following: length of listening activity for a song, length of listening activity for an album, and user actions during song or album play, such as fast forwarding, track skipping, stopping or pausing the song, or other media plays, such as websites visited, book titles, movies watched, playing activity during a movie or other presentations, ratings, or terms corresponding to the media, such as “comedy”, “sexy”, etc. 
     A taste profile can represent a single user or multiple users. Conversely, a single user or entity can have multiple taste profiles. For example, one taste profile could be generated in connection with a user&#39;s song play activity, whereas another separate taste profile could be generated for the same user based the user&#39;s selection of songs/artists for a playlist. 
     In addition, taste profile data can also contain third party data about users (anonymous or otherwise) via the use of key-value information. For example, social media sites can be examined to create anonymous users and anonymous taste profiles based on mentions of a song title or an artist. In another example, a third-party audio streaming service can update taste profiles based on song “events”, such as streaming of a new song. 
     Users or entities need not be aware what the taste profile is being used for. For example, statistics in a taste profile can be used with statistics from other taste profiles to predict demographic groups corresponding to song plays, without requiring any active submission from a user or client device regarding the user&#39;s demographics. Moreover, publicly available data can be included in the taste profile, providing an additional source of easily obtained data which can be used for more robust predictions. 
     An artist name or song title in a taste profile may be resolved from multiple different textual representations in a taste profile. For example, an artist or song might be commonly represented by multiple nicknames, abbreviations, formats, misspellings, aliases, and the like. Accordingly, the system may take raw text which might include these abnormalities and resolve them to a formal artist or song title. Such resolution could be performed in a server performing other aspects of the invention, or could be performed off-site in another device. 
     In addition, priority or preference values for a particular song or artist can be stored in the taste profile and can be weighted more heavily if, for example, an artists or song is listened to more frequently, or if a user has identified favorite artists or songs. 
     While the disclosure refers mainly to using musical data such as artist name or song title for purposes of clarity, it should be understood that the disclosure is not limited thereto. In particular, demographic data could be predicted based on another media preference (e.g., book, movie or game preference) instead of musical data. For example, mentions from social media networks, user settings, playlists or favorites lists can be obtained by crawling or mining this information from the web or other user data to determine preferences related to types of content other than music, for example, book, movie or game titles. Thus, according to the invention, the data set and corresponding terms and weights can be one of a musical data set, a book data set, a movie data set, a game data set, or some combination thereof. 
     In one embodiment, user preference data is independent of a taste profile, and is simply be gathered based on generic data analysis (e.g., number of mentions, etc.). Thus, in such an embodiment, a prediction is based on the book, movie or game data. 
     In one example, the taste profile database  103  is updated continuously. For example, a record is added when a user listens to a new song, and the record is updated when an update of the user preference for the song is received via a client device. In one embodiment, the information received from the client device is stored in the database, the correct “matched” metadata is added, and a play count is initialized. For example, a taste profile update with “Britney Spears—Oops” gets resolved to the actual song ID and metadata for “Britney Spears” and “Oops, I Did It Again”, with a play count of  1 . If a fingerprint code (e.g., an audio fingerprint code) is sent to initialize a taste profile item, the system can resolve the fingerprint code to metadata and discard the fingerprint code. 
     Referring back to  FIG. 1 , taste profiles  103  contains records indicating the music taste (or other tastes) of users. Each taste profile is a representation of musical activity, and may include a wide range of information. Taste profiles  103  can be implemented as one or more relational databases or in any other way that allows fast query processing and scaling. 
     Returning to  FIG. 3 , a record  301  in taste profiles  103  contains a taste profile ID  303  corresponding to a user. The record  301  may further contain various fields identifying a song, such as an artist ID  305  identifying the performer of the song, a play count  307 , and an album number or track number identifying the medium of the song (not shown). In addition, the record  301  may contain various fields indicating a user&#39;s affinity for the song, such as a play count  307  and a review. 
     Each record  301  in the taste profile is used to produce, for each taste profile ID  303 , a list of terms, where the length of the list generally ranges between  1  and  100 , 000 . Each record  301  can be implemented as a covering index residing in RAM for fast random access by management modules  101 . 
     Referring to  FIGS. 1 and 4 ,  FIG. 4  illustrates a representative view of inverted indices stored in data source  105 , which is an index database containing records as inverted indices in which terms are indexes to documents. Of course, records can be implemented in any other way that allows fast retrieval of desired information. An inverted index  403  can be generated for any term that appears in the documents in the document database  107 . The term is then mapped to the list of documents that contain the term. The inverted indices in data source  105  allow the artists, songs or other subjects in music domains that might be associated with terms corresponding to a user&#39;s music experience to be identified quickly. 
     As discussed above, the system also contains an application programming interface (API)  109 . Functionally, the API  109  takes a request from a client device, and authenticates users included in the request against the user database  111 . Upon successful authentication, the request is passed to the management module  101 . After the management module  101  performs processing to fulfill the request and sends the processing result back to the network, the API  109  outputs the processing result to the client device. 
     Other databases (not shown) may be communicatively linked to management modules  101 . Such additional databases may store music requests each corresponding to one or more users, each representing a list of documents over a specific domain that is associated with specific users. Still other databases may contain records mapping a user to the list of records in the taste profile database  103 . 
     As described more fully below, a wide range of terms and weights associated with each artist or song can be accessed in connection with a wide range of data in the taste profiles. This combination provides for a more robust prediction of demographic data from the taste profile data. 
       FIG. 5  is a flowchart diagram showing an exemplary procedure for predicting data. Generally, this exemplary embodiment predicts demographic data from a wide range of information corresponding to the artist or song title. A name or title is obtained from a taste profile. An index into a data set is included, which is based on the name or title. A set of terms and corresponding term weights associated with the artist name or song title are retrieved from the profile, and the terms and term weights are used to construct a sparse vector. The sparse vector is input to a training model including target data, where the target data includes a subset of test data which has a correspondence to a predetermined target metric of data (e.g., demographic data). In turn, a respective binary value and confidence level is output for each term, corresponding to an association between the term and the target metric. In that regard, the value does not need to be binary. For example, regression can be performed with a class such as “income” or “age” on a 0 . . . 1 scale with truth vectors having explicit numbers instead of a binary yes/no. 
     In more detail, in step  501 , an artist or song title is obtained from a taste profile. While the disclosure herein may refer to a single artist or song title for purposes of conciseness, it should be understood that the demographic prediction might often be from multiple artists or song titles. For example, in one embodiment, the demographic data may be predicted for all of the artists or song titles in a taste profile or across multiple taste profiles. 
     A taste profile is a representation of musical activity, and includes a wide range of information such as playlists, play counts, start/stop/skip data for portions of a song or album, contents of collections, user rankings, preferences, or mentions, etc. A taste profile can represent a single user or a multiple users. Conversely, a single user or entity can have multiple taste profiles. For example, one profile could be generated in connection with a user&#39;s song play activity, whereas another separate profile for the same user could be generated based on the user&#39;s selection of songs/artists for a playlist, among others. Moreover, publicly available data can be tied to the taste profile. For example, social media sites can be examined to create anonymous users and anonymous taste profiles. 
     Returning to  FIG. 5 , in step  502 , terms and weights associated with each artist or title in the taste profile are retrieved. A database may store a wide range of terms associated with each artist name or song title. For example, one example embodiment might include over 10,000 terms for each artist and associated weights, based on how important, how often mentioned or how closely related the term is to the artist, including location, genre and style, biography, recent news articles, time-dependent popularity and familiarity data, cultural analysis data, and son on. For example, the artist “Beyonce” might be associated with a vector of terms including “fast tempo”, “R&amp;B”, “sexy” etc., with corresponding weights of 4.5, 4.2 and 2.5. Additional information regarding generation of terms and weights can be found in U.S. Pat. No. 7,772,478, entitled “Understanding Music”, the contents of which are incorporated by reference herein. By tapping into a larger amount of data associated with the artist or song names, it is ordinarily possible to predict more accurately than just using, for example, the song title alone. In particular, as discussed above, the usage of a song, artist, movie, etc. in a taste profile to determine predictive qualities can be enhanced by expanding these media items into descriptive terms and using those terms as the inputs to the predictive model. 
     In step  503 , a sparse vector is constructed based on the obtained terms and weights. In particular, each non-zero term corresponding to the artist or song title (or each artist or song title, if there are multiple) is combined to form a vector, with each dimension of the vector being a retrieved term, e.g., “sexy”. Thus, in one aspect, the taste profile includes multiple artists or song titles, and the sparse vector is constructed from all of the terms in the musical data set corresponding to all artists or songs in the taste profile. As such, from one perspective, the sparse vector represents an entity&#39;s (e.g., a user&#39;s) musical identity. All non-zero terms across all artists in the taste profile are combined to form the vector. In one embodiment, if terms overlap between artists, e.g., both Beyonce and Michael Jackson correspond to “R&amp;B”, the weight of that term can be increased by, for example, adding the individual weights together for that term, by multiplying the probabilities, or by placing them in a Gaussian or other distribution and normalizing them, among other methods. 
     In step  504 , the sparse vector is input to a training model, for example by a support vector machine (SVM). The training model is based on machine learning from ground truths from a random selection of data where target (demographic) data has been filled in and is held back during evaluation so that the evaluation task has never seen the input data before. For example, a training model might use a database of one million taste profiles, which, as mentioned above, include snapshots of detailed listening activity and artist preference, alongside other demographic data and media preference data from various publicly available sources. One half of the one million might be test data for which certain ground truths are known, i.e., person x likes classical and country music, and falls under the demographic categories of male and 25-40 years of age. In an exemplary embodiment, the test data has an even distribution of false and positive examples, e.g., half of each. 
     Exemplary data found in a training model is shown below, with the artist and song plays as the source data, and the remaining fields listing target demographic metrics. 
     
       
         
           
               
               
             
               
                   
               
               
                 Field 
                 Exemplary Data 
               
               
                   
               
             
            
               
                 Musical artist 
                 [“Aerosmith”: 10, “Lindstrom”: 5, 
               
               
                 (boosted by weight) 
                 “David Bowie”: 2] 
               
               
                 Song plays 
                 [“Band on the Run”: 14, “Fire”: 3, 
               
               
                   
                 “Stairway to Heaven”: 9] 
               
               
                 Gender 
                 male, female, unknown, not specified, etc 
               
               
                 Movie preference 
                 [“Stalker”, “Until the end of the world”, 
               
               
                   
                 “The Rock”] 
               
               
                 Book preference 
                 [“Vineland”, “The Tin Drum”, “The Girl 
               
               
                   
                 With the Dragon Tattoo”] 
               
               
                 Locale 
                 US, UK, Georgia, Hillsdale, NJ, 02141, etc 
               
               
                 Music service type 
                 Spotify, iTunes, Rdio, MOG, none, etc 
               
               
                 Political figure 
                 Democrat, Republican, Ron Paul, Mitt Romney, etc 
               
               
                 or party 
               
               
                 Age 
                 18, 45, unknown, etc 
               
               
                 Marital status 
                 married, single, etc 
               
               
                   
               
            
           
         
       
     
     Many more fields can be collected or generated as training data, such as, for example, sports affinity, food and beverage brand types mentioned (e.g., in a social media profile), video game console or game preference, college/university, and so on. For these taste profiles used in the learning model, there is ordinarily little or no need to collect names or any other directly identifiable information. Thus, for example, each taste profile may be anonymized and given an ID and any other demographic or media preference data can be stored elsewhere linked to the taste profile. 
     Of course, depending on the taste profiles used as the test data, not every taste profile need have a full complement of target data. For example, while almost all taste profiles may include some locale data, perhaps only 90% might include gender, only 40% might include media preference, only 10% might include music service, only 20% might include political, and only 60% might include age. As discussed below, therefore, the F 1  measure for accuracy can be used for evaluation, whereas sampling bias can be reduced in the classifier by choosing an equal amount of pro/con (positive/negative) examples during training. For example, if only 10% include a music service, the test data can use 20% of usual. 
     Thus, the test data can comprise a set of data determined to be associated with the target metric, as a ground truth for the learning model. The learning model trains on these ground truths, and then predicts demographics for new (input) taste profiles based on the model. Each target metric (e.g., male gender) is treated as a binary classification with multiple buckets each being a separate classifier, although regression is possible for certain classes (age, location) to get mean absolute error (MAE) instead of an F 1  measure. The training model may use support vector machines (SVM) to train a model of profiles to a class output. For example, multiple instances of a taste profile can be used, and a non-linear distance function (e.g., the kernel method) can be used as a target function. The value of the evaluation kernel for new data is the “score” for the affinity between a new taste profile and the target. In the learning model, a linear SVM can be used for Vector A and a Gaussian RBF kernel SVM can be used for Vector B. Automatic regularization detection can also be used as described in U.S. Pat. No. 7,772,478. 
     In step  505 , the training model may give an output class of  0  or  1  (positive or negative) for each input sparse vector, along with a confidence interval from the SVM classifier expressed as an absolute value. A positive output class indicates that this taste profile is part of the class predetermined in the ground truth (e.g., male gender), and the absolute value is the amount of confidence in that relation between the taste profile and the class. In some aspects, the confidence value associated with the SVM classifier could be used to filter results. For example, results or output could be filtered to only those terms with a confidence level above a set threshold. In such a case, a tradeoff between accuracy and coverage can be managed by varying the threshold. 
     In step  506 , the artist or title (or all of the artists or titles in the sparse vector) can be evaluated as a classifier based on the output. For example, the system may examine the predictions using, for example, an F 1  measure or false positive/negative rates, etc., to determine the accuracy of the prediction for a given song title or album name. The F 1  measure computes a single blended measure of precision (how often the prediction was relevant) and recall (how much of the relevant data was correctly predicted). Therefore, if very few of the test set is over the age of 80, a “dumb” classifier could simply never predict that age bracket and get very high scores—F 1  counters this by figuring in the statistics of the dataset. An F 1  score of  1  in the evaluation of a predictive model indicates a perfect classifier or accuracy whereas an F 1  of  0  is always incorrect. It can be interpreted as a probability of getting the prediction right taking sampling bias into account, and is defined as F 1 =2·((precision·recall)/(precision/recall)). 
     Thus, as described above, the usage of a song, artist, movie, etc. in a taste profile to determine predictive qualities can be enhanced by expanding these media items into descriptive terms and using those terms as the inputs to the predictive model. 
     In another example embodiment, graph data from social networks can be utilized to build predictive models of audience segmentation or brand affinity, based on media preference (e.g. music taste). Thus, according to this embodiment, the target metric can be a segment or brand affinity (e.g., “concerts” or “TicketMaster™”). However, segment or brand affinity may be more difficult to predict from artist names or song titles alone. Accordingly, in this embodiment, the predictive model can be enhanced by using follower graph data from social networks. 
     In more detail, by crawling follower graph data from social networks, it is possible to automatically build predictive models of audience segmentation or brand affinity based on media preferences in the social network data. As used herein, a “segment” refers to one or more individual brands or accounts. For example, a segment such as “concerts” may contain many brands such as particular venues or ticketing companies. 
     As mentioned above, according to this embodiment, the target metric is a brand or segment affinity. For example, it may be desirable to determine if a particular user has an affinity for TicketMaster™. Since musical data embedded in a taste profile may not necessarily be sufficient to easily predict such brand or segment affinity, this embodiment gathers musical affinity data from social networks to aid in the prediction. 
     In that regard, many social networks and media sites expose a “social graph”—the connections between friends, followers, and concepts or media or brands that the person chooses to like or follow. For example, on the social networking site Twitter™, a particular user&#39;s graph is defined as the set of accounts they follow or are following. For example, a Twitter™ account can follow a musician, a brand, a publication, or other people. As such, it is possible to quickly gather connections between musicians and other brands by finding colocation in the graph for large amounts of people or accounts. 
     Briefly, according to the embodiment, a name or title is obtained from a taste profile. There is an index into a data set based on the name or the title, and a set of terms and corresponding term weights associated with the name or the title are retrieved. A sparse vector is constructed based on the set of terms and term weights. A target brand or segment of interest is identified. A first list of accounts who follow the brand or segment of interest is generated by examining social media data, and a second list is generated of what additional entities are followed by accounts in the first list. The second list is filtered through a space mapping that maps entities to names or titles from taste profiles, to generate a subset of test data having a correspondence to the target brand or segment of interest. The sparse vector is input to a training model including target data. The target data includes the subset of test data having a correspondence to the target brand or segment of interest. A respective binary value and confidence level for each term, corresponding to an association between the term and the target brand or segment of interest. 
     Thus, according to this embodiment, the processes described above (e.g. with respect to  FIGS. 1 to 5 ) are enhanced with graph data from social networks to build predictive models of audience segmentation or brand affinity. 
     First, brands or segments of interest are identified. A segment can contain many individual brands or accounts. For example, a segment for “concerts” can contain multiple venues or ticketing companies. 
     Next, a list of accounts (e.g., people) who follow that the brands or segments of interest are retrieved, in a random sampling fashion. For example, at a particular point in time, TicketMaster™ is followed by 118,000 people, and a number of these accounts may be retrieved for a predictive model. In that regard, the number of accounts selected for the list of accounts may be a function of the size of the data, the complexity of the problem, and so on. For example, in one example case only 5,000 accounts or so may be necessary to generate a good predictive model, but in more complex cases, more may be necessary. Thus, in one aspect, a first list of accounts is generated by selecting people who follow the target brand or segment of interest in a random sampling fashion. Nevertheless, in some cases, the sampling may not be exactly “random”, as the sampling may include additional features such as choosing or filtering for “quality” users (e.g., non-spammers or fake accounts) and the like. 
     Once the (first) list of accounts has been obtained, a second list is generated by determining additional entities that are followed by the accounts comprising the first list. The second list is filtered through an ID space mapping that maps entities to names or titles from taste profiles. Thus, for example, it can be determined that a random account follows Ticketmaster™ and a set of musicians. 
     The ID space mapping, generally, is a method to convert an artist name or song title or a song analysis to a unique identifier that can be used across many different databases. The unique identifier has a high probability of being actually unique, that is, there is low chance of overlap due to a song of a different quality or an artist misspelling or collaboration. The identifier can be used to translate between other database entries and formats that a user or administrator might not have control over. 
     In that regard, as mentioned above, a database might contain entries for millions of artists or songs from a variety of sources. For example, a system or user may crawl the web to find new artist names and songs, work with partners that deliver new catalogs on a weekly basis, or take in data from customers over an application program interface. As such, when dealing with data from dozens of sources, it is useful to efficiently connect a simple text string to the rest of the database. 
     Therefore, in one embodiment, an ID space mapping scheme has a one-to-one mapping between a musical entity (e.g., artist or song title) and an ID, where different components provide different information. 
     For example, an example ID might be “ARHAWPX1187B99274F”. In this example, “AR” might correspond to a “type code” indicating the type of entity being represented by the ID. Thus, in this example embodiment, artists might be represented by “AR”, for songs, “SO”, releases, “RE”, and so on. Thus, the type code is, in this example, a two letter code that identifies the type in the ID itself, which helps quickly identify without a database lookup what entity the ID refers to. The next component in the example ID above, “HAWPX”, can be a random string generated by a machine on boot of a process that generates new IDs. This string is formed from a dictionary of upper case letters. The random generator triggers once per process, and allows a user or system to trace back an ID generator to the process. The final component in the example ID above, “1187B99274F”, is a hexadecimal representation of the time in the operating system since the UNIX epoch, with an assurance that if the time is the same as the last generated ID, 1 is added to the number. Naturally, it should be understood that the above scheme is simply an example, and other schemes and/or mappings could be used. 
     The random string may be compressed to 24 bits using hexavigesimal encoding and combined with the ten least significant digits of a time code to provide a 64-bit ID number which is useful for database storage. 
     When songs are the musical entity for one-to-one ID mapping, the system might take into account a more specific definition of a “song” for a more robust set of data. For example, a “song” might be defined specifically as a single recorded work, such that a live version of a song and the original song get different IDs, or a cover version of a song (same composition ID) has a different song ID than the original. In addition, input song files might be referred to as “tracks” (type code TR) to delineate them from songs. In particular, a song has many tracks, often hundreds, with each one slightly different, such as different radio edits, mastering, re-releases, different encodings, and the like. 
     In that regard, any input new track can be processed to create an audio fingerprint, which is matched against the closest matching track. The track&#39;s song can then be looked up, and the new track can be assigned same song ID, whereas if there is no matching track, a new song ID can be created. By virtue of this arrangement, it is ordinarily possible to ensure that only unique recorded works have song IDs. 
     In another example aspect, when an artist name is received, the artist name is matched against a database (e.g., an artist database), which might contain many instances of aliases, misspellings and foreign spellings. Accordingly, a text indexing system can be used to quickly match out a few candidates and then filter using a set of rules. For example, rules might include replacing punctuation like “\&amp;” with “and”, etc., using metaphone or soundex “sounds-like” matching to see if words were spelled incorrectly, and removing stop words like the, or “D.J”. If given both songs and artists, the song data can be used to see if a differently spelled artist has songs with that title. If the artist names are close enough, the artist in the database can be considered a match. If a match is not found, a new AR ID is created for the artist. 
     In addition, sets of artists and songs may be input from partners and customers. A table of the native ID scheme can be maintained alongside the newly generated ID. Thus, partners or customers can query for data with any other foreign ID. Quite often, due to the high quality nature of a fingerprint, many tracks from a customer might point to the same song. If a “foreign” ID is used that points to an expired or merged ID, the foreign ID can be redirected to the proper canonicalized ID, and the multiple track IDs from a customer can be reported given a single unique song ID. 
     Notwithstanding the above, in some cases, records may need to be updated or deleted. For example, merges (two separate IDs that were determined to be the same entity) can be tracked by a table that keeps the old ID around. If a user queries for a merged-out ID, the proper (new) ID can be returned instead. In another example, if an entity is deleted, the corresponding ID can be maintained so it is not reused. 
     Meanwhile, an accurate match between a social media account and a corresponding artist name and identifier can be obtained, for example, using a combination of web crawling and/or artist name matching as described in U.S. patent application Ser. No. 13/850,044, entitled “Named Entity Extraction From a Block of Text”, the contents of which are incorporated by reference herein. 
     Accordingly, an addition to the taste profile (or new taste profile) can be generated, in which each account has a set of n artists as well as a brand or segment affiliation. The taste profile can then be used to train a predictive model as described above, adding new segments or brands whenever needed. 
     According to another aspect of the above embodiment, spam detection or other measures may be added in order to identify and eliminate for false or misleading information, and in particular, to eliminate false or suspicious accounts. In this regard, many accounts on social networks may be false, either to boost numbers for a brand or to spam users with messages. For example, 10,000 followers of a particular brand might appear to all follow the exact same set of people, and all appear to have fake names. Thus, false or suspicious accounts can be identified by, for example, examining the number of accounts that follow suspicious accounts (e.g., whether the account has less than a threshold number of followers), or by determining how active the accounts are on the social network in question (e.g., whether the account has less than a threshold amount of activity). The false or suspicious account can then be eliminated. 
     Accordingly, by crawling follower graph data from social networks, it is possible to automatically build predictive models of audience segmentation or brand affinity based on media preferences in the social network data. 
     The above embodiments have been generally described with respect to prediction, using a learning model trained on taste profiles with at least some ground truths. 
     Nevertheless, the invention is not limited to prediction based on ground truths or predetermined labels. In particular, the machine learning can also be conducted without ground truths. In such a case, clusterings (or “latent clusters”) are produced instead of predictions. For example, the system may find that people that listen frequently to classical music also tend to listen earlier in the morning, people who listen for less than a minute to each song tend to not pay bills, etc. Accordingly, in such an embodiment, the output is generally a clustering of behavioral data. Put another way, it is ordinarily possible to cluster a taste profile representative of all the music activity of one or more users into, for example, taste groups (e.g., 80s, country, R&amp;B) or affinity groups (e.g., influencer, hipster, mainstream). 
     Taste profiles can be clustered into useful buckets using an unsupervised method, i.e., one without predetermined ground truths. This method inputs a large set of taste profile data and uses an unsupervised clustering approach that creates k new buckets to place new data in (with k being chosen beforehand). Unsupervised clustering finds latent variables in data, and may show new ways of categorizing an audience, although the buckets are not labeled in any necessarily understandable way. 
     Thus, in another example embodiment, latent taste clusters are generated from taste profile data corresponding to one or more anonymous users and including at least an artist name or a song title. An artist name or a song title is obtained from a taste profile stored in taste profile data corresponding to one or more anonymous users. There is an index into a musical data set based on the artist name or the song title, and a set of terms and corresponding weights associated with the artist name or the song title are retrieved. A sparse vector is constructed based on the terms and term weights. The sparse vector is input to a clustering procedure, and one or more latent taste clusters are output based on the clustering. 
     A taste clustering prediction procedure such as that mentioned above could operate on the same data as for the demographic prediction procedure, with the exception that there is no ground truth (i.e., no training data is required). The clustering procedure could comprise, for example, K-means or Latent Dirichlet Allocation (LDA) clustering trained on taste profile data to represent hidden variables in the group of profile data. The results can be evaluated, for example, by seeing how cleanly the generated clusters maintain divisions, such as whether folk music and rock music remained neatly segregated between clusters. 
       FIGS. 6A to 6G  are representative views of results from predicting demographic data according to example embodiments. 
       FIG. 6A  shows demographic data predicted based on simple data. For example, as shown in  FIG. 6A , age bracket and gender can be predicted from web browsing data, e.g., sites visited and the content of the sites visited, reaching F 1  scores of 0.8 for gender and 0.4 for age bracket. Meanwhile, predicting gender from writing style on movie reviews reaches an accuracy of about 73%. In still another example, log material such as page title and IP address is matched against registration data from a news website, yielding a break-even point of 0.7 for gender and 0.42 for age bracket. 
       FIGS. 6B to 6G  depict various sample outcomes according to example embodiments of the invention. 
     In  FIGS. 6B to 6G , Vector A is a vector based merely on the words making up the names of artists or songs that a user has listened to, and is shown for comparison with the more robust Vector B. Vector B corresponds to the more robust sparse vector discussed above, namely, based on a database storing, e.g., over 10,000 terms for each artist and/or song, along with associated weights. 
     More specifically,  FIGS. 6B to 6G  depict the differences between two vectors of each taste profile representing the music listening as the input to the training model. Vector A is a “bag of words” term approach where every song or artist either exists or does not exist. For example, anonymous user X is represented as [“Aerosmith”:1, “Beyonce”:1, “Barbra Streisand”:1]. Any artist the user did not mention or listen to is not included and assumed to be  0 . 
     Meanwhile, Vector B takes far more data for all of those artists and songs and arranges it in a far more descriptive set of musical data, including genre descriptors, similar artists, words used to describe the artists and songs, popularity, and so on. The vector B data is composed of a combination of artist data with weights with term data from cultural analysis as described above and in U.S. Pat. No. 7,772,478. 
     As mentioned above, in the learning model, a linear SVM can be used for Vector A and a Gaussian RBF kernel SVM can be used for Vector B. Automatic regularization detection can also be used as described in U.S. Pat. No. 7,772,478. 
     For each target type (age, gender, etc),  FIGS. 6B to 6G  depict accuracy on the vector A approach and the vector B approach, alongside (in some cases) other methods. Some target types such as movie and book preference require bucketing into genre/style specific clusters. 
     For gender ( FIG. 6B ), with more music data a significant boost in prediction quality can be seen. For example, according to this example, gender can be predicted with an F 1  of 0.84 using the extended musical features. 
     Age predictions ( FIG. 6C ) were bracketed into “25 and under” and then “25 to 35.” While simple music listen data handily beats a log data analyzer, the extended data does even better at an F 1  of 0.88. 
     For the film preference task ( FIG. 6D ) movies were bucketed into genre and chose to predict the top 3 movie genres found in the set: comedy, romance and crime. The F 1  score shows the accuracy of preference prediction for that genre of movie based on simple music data alone (Vector A) and then with extra music data (Vector B.) It can be observed that music is a relatively good predictor of comedy movie preference, good at romance movie prediction, and not so good at crime movie prediction. On the other hand, the extra musical data may not help the crime movie prediction task as much in this example, possibly because distribution of crime movie preference bridges across music taste. 
     The music service task ( FIG. 6E ) looked at anonymous users who listed a preference for a music service like Spotify, Rdio, Rhapsody or MOG, vs. not mentioning one (or having any activity related to such a service) and then the same for radio services such as iHeartRadio or Pandora. Music preference seems to be a reliable predictor for subscribing to a radio service, but perhaps not yet for a streaming service. The Vector A approach on streaming received an F 1  of 0. 
     For prediction of political leaning ( FIG. 6F ), preferences were examined for political figures or parties—e.g., if a user&#39;s taste profile listed “Barack Obama”, the profile is placed in the “democratic” bucket, or if they listed the Democratic party as a membership or social media “like” or mention. Likewise, mention of prominent Republican figures or the party placed them in the “republican” bucket. This experiment was set up as a binary decision tree so the score represents accuracy of predicting a self-selected party affinity in the reductive case of having to choose between two parties. The system achieved a respectable F 1  of 0.351 predicting this purely on our extended musical data and 0.237 on the Vector A artist data. 
     Relationship status ( FIG. 6G ) ordinarily comes from a lot of messy data from various sources. This data was cleaned as best as possible and three major buckets were identified: “single,” “married” and “in a relationship.” For example, “seeing someone” or “engaged” went to “in a relationship,” “alone forever” went to ‘single,” “domestic partnership” went to “married” and so on. It can be seen that while it is difficult accurately predicting married vs. not or “in a relationship”, there is better performance at predicting single (again, note that the score does take into account the very high bias of our test set mostly self reporting as “single.”). In this case, additional music data being gathered may help. 
       FIG. 7  is a block diagram of a general and/or special purpose computer  700 , which may be a general and/or special purpose computing device, in accordance with some of the example embodiments of the invention. The computer  700  may be, for example, a user device, a user computer, a client computer and/or a server computer, among other things. 
     The computer  700  may include without limitation a processor device  710 , a main memory  725 , and an interconnect bus  705 . The processor device  710  may include without limitation a single microprocessor, or may include a plurality of microprocessors for configuring the computer  700  as a multi-processor system. The main memory  725  stores, among other things, instructions and/or data for execution by the processor device  710 . The main memory  725  may include banks of dynamic random access memory (DRAM), as well as cache memory. 
     The computer  700  may further include a mass storage device  730 , peripheral device(s)  740 , portable non-transitory storage medium device(s)  750 , input control device(s)  780 , a graphics subsystem  760 , and/or an output display interface  770 . For explanatory purposes, all components in the computer  700  are shown in  FIG. 7  as being coupled via the bus  705 . However, the computer  700  is not so limited. Devices of the computer  700  may be coupled via one or more data transport means. For example, the processor device  710  and/or the main memory  725  may be coupled via a local microprocessor bus. The mass storage device  730 , peripheral device(s)  740 , portable storage medium device(s)  750 , and/or graphics subsystem  760  may be coupled via one or more input/output (I/O) buses. The mass storage device  730  may be a nonvolatile storage device for storing data and/or instructions for use by the processor device  710 . The mass storage device  730  may be implemented, for example, with a magnetic disk drive or an optical disk drive. In a software embodiment, the mass storage device  730  is configured for loading contents of the mass storage device  730  into the main memory  725 . 
     The portable storage medium device  750  operates in conjunction with a nonvolatile portable storage medium, such as, for example, a compact disc read only memory (CD-ROM), to input and output data and code to and from the computer  700 . In some embodiments, the software for storing information may be stored on a portable storage medium, and may be inputted into the computer  700  via the portable storage medium device  750 . The peripheral device(s)  740  may include any type of computer support device, such as, for example, an input/output (I/O) interface configured to add additional functionality to the computer  700 . For example, the peripheral device(s)  740  may include a network interface card for interfacing the computer  700  with a network  720 . 
     The input control device(s)  780  provide a portion of the user interface for a user of the computer  700 . The input control device(s)  780  may include a keypad and/or a cursor control device. The keypad may be configured for inputting alphanumeric characters and/or other key information. The cursor control device may include, for example, a handheld controller or mouse, a trackball, a stylus, and/or cursor direction keys. In order to display textual and graphical information, the computer  700  may include the graphics subsystem  760  and the output display  770 . The output display  770  may include a cathode ray tube (CRT) display and/or a liquid crystal display (LCD). The graphics subsystem  760  receives textual and graphical information, and processes the information for output to the output display  770 . 
     Each component of the computer  700  may represent a broad category of a computer component of a general and/or special purpose computer. Components of the computer  700  are not limited to the specific implementations provided here. 
     Software embodiments of the example embodiments presented herein may be provided as a computer program product, or software, that may include an article of manufacture on a machine accessible or machine readable medium having instructions. The instructions on the non-transitory machine accessible machine readable or computer-readable medium may be used to program a computer system or other electronic device. The machine or computer-readable medium may include, but is not limited to, floppy diskettes, optical disks, CD-ROMs, and magneto-optical disks or other type of media/machine-readable medium suitable for storing or transmitting electronic instructions. The techniques described herein are not limited to any particular software configuration. They may find applicability in any computing or processing environment. The terms “computer-readable”, “machine accessible medium” or “machine readable medium” used herein shall include any medium that is capable of storing, encoding, or transmitting a sequence of instructions for execution by the machine and that cause the machine to perform any one of the methods described herein. Furthermore, it is common in the art to speak of software, in one form or another (e.g., program, procedure, process, application, module, unit, logic, and so on) as taking an action or causing a result. Such expressions are merely a shorthand way of stating that the execution of the software by a processing system causes the processor to perform an action to produce a result. 
     Portions of the example embodiments of the invention may be conveniently implemented by using a conventional general purpose computer, a specialized digital computer and/or a microprocessor programmed according to the teachings of the present disclosure, as is apparent to those skilled in the computer art. Appropriate software coding may readily be prepared by skilled programmers based on the teachings of the present disclosure. 
     Some embodiments may also be implemented by the preparation of application-specific integrated circuits, field programmable gate arrays, or by interconnecting an appropriate network of conventional component circuits. 
     Some embodiments include a computer program product. The computer program product may be a storage medium or media having instructions stored thereon or therein which can be used to control, or cause, a computer to perform any of the procedures of the example embodiments of the invention. The storage medium may include without limitation a floppy disk, a mini disk, an optical disc, a Blu-ray Disc, a DVD, a CD or CD-ROM, a micro-drive, a magneto-optical disk, a ROM, a RAM, an EPROM, an EEPROM, a DRAM, a VRAM, a flash memory, a flash card, a magnetic card, an optical card, nanosystems, a molecular memory integrated circuit, a RAID, remote data storage/archive/warehousing, and/or any other type of device suitable for storing instructions and/or data. 
     Stored on any one of the computer readable medium or media, some implementations include software for controlling both the hardware of the general and/or special computer or microprocessor, and for enabling the computer or microprocessor to interact with a human user or other mechanism utilizing the results of the example embodiments of the invention. Such software may include without limitation device drivers, operating systems, and user applications. Ultimately, such computer readable media further includes software for performing example aspects of the invention, as described above. 
     Included in the programming and/or software of the general and/or special purpose computer or microprocessor are software modules for implementing the procedures described above. 
     While various example embodiments of the present invention have been described above, it should be understood that they have been presented by way of example, and not limitation. It will be apparent to persons skilled in the relevant art(s) that various changes in form and detail can be made therein. Thus, the present invention should not be limited by any of the above described example embodiments, but should be defined only in accordance with the following claims and their equivalents. 
     In addition, it should be understood that the  FIGS. 1-7  are presented for example purposes only. The architecture of the example embodiments presented herein is sufficiently flexible and configurable, such that it may be utilized (and navigated) in ways other than that shown in the accompanying figures. 
     Further, the purpose of the foregoing Abstract is to enable the U.S. Patent and Trademark Office and the public generally, and especially the scientists, engineers and practitioners in the art who are not familiar with patent or legal terms or phraseology, to determine quickly from a cursory inspection the nature and essence of the technical disclosure of the application. The Abstract is not intended to be limiting as to the scope of the example embodiments presented herein in any way. It is also to be understood that the procedures recited in the claims need not be performed in the order presented.