Data and information pertaining to events, circumstances, and entities in various types of domains, such as sports, business and finance, crime, education, real estate, etc., is readily available. The subject invention functions to use such available data and information to automatically create narrative stories that describes domain event(s), circumstance(s) and/or entity(ies) in a comprehensible and compelling, e.g., audience customized, manner.
For automatically generating a narrative story hereinafter is described in greater detail a system and method that functions to receive data and information pertaining to domain event(s), circumstance(s), and/or entity(ies), i.e., domain related data and information, use the received domain related data and information to determine one or more derived features for the domain event(s), circumstance(s), and/or entity(ies), i.e., domain related derived features, use the received domain related data and information and/or one or more domain related derived features to identify one or more angles for the narrative story, filter the plurality of angles for the narrative story, select, retrieve, assemble and order facts or points associated with the filtered plurality of angles for the narrative story, and render the narrative story using the filtered plurality of angles and the assembled points.
While the forgoing provides a general explanation of the subject invention, a better understanding of the objects, advantages, features, properties and relationships of the subject invention will be obtained from the following detailed description and accompanying drawings which set forth illustrative embodiments and which are indicative of the various ways in which the principles of the subject invention may be employed.
For a better understanding of the subject invention, reference may be had to preferred embodiments shown in the attached drawings in which:
A system and method for using data and information pertaining to event(s), circumstance(s), and/or entity(ies) in a domain or domains, e.g., sports, business, financials, crime, education, medical, census, social indicators, etc., to automatically create narrative stories is hereinafter described. As shown in
For performing the various tasks in accordance with the executable instructions, the processing device 20 preferably includes a processing unit 22 and a system memory 24 which may be linked via a bus 26. Without limitation, the bus 26 may be a memory bus, a peripheral bus, and/or a local bus using any of a variety of bus architectures. As needed for any particular purpose, the system memory 24 may include read only memory (ROM) 28 and/or random access memory (RAM) 30. Additional memory devices may also be made accessible to the processing device 20 by means of, for example, a hard disk drive interface 32, a magnetic disk drive interface 34, and/or an optical disk drive interface 36. As will be understood, these devices, which would be linked to the system bus 26, respectively allow for reading from and writing to a hard disk 38, reading from or writing to a removable magnetic disk 40, and for reading from or writing to a removable optical disk 42, such as a CD/DVD ROM or other optical media. The drive interfaces and their associated computer-readable media allow for the nonvolatile storage of computer readable instructions, data structures (e.g., data and information that is to be used to generate a story), program modules and other data for the processing device 20. Those skilled in the art will further appreciate that other types of computer readable media that can store data may be used for these same purposes. Examples of such media devices include, but are not limited to, magnetic cassettes, flash memory cards, digital videodisks, Bernoulli cartridges, random access memories, nano-drives, memory sticks, and other read/write and/or read-only memories.
A number of program modules may be stored in one or more of the memory/media devices. For example, a basic input/output system (BIOS) 44, containing the basic routines that help to transfer information between elements within the processing device 20, such as during start-up, may be stored in ROM 28. Similarly, the RAM 30, hard drive 38, and/or peripheral memory devices may be used to store computer executable instructions comprising an operating system 46, one or more applications programs 48 (such as application programs that function to create a story from domain event data and information, provide a user interface that allows a user to specify parameters for use in generating a customized, narrative story, etc.), other program modules 50, and/or program data 52. Still further, computer-executable instructions may be downloaded to one or more of the computing devices as needed, for example, via a network connection.
An end-user or operator, may enter commands (e.g., to customize narrative stories to an intended audience, etc.) and information (e.g., to key in data and/or information to be used in generating narrative stories, to indicate the logical location of that information in a network or file system, etc.) into the processing device 20 through input devices such as a keyboard 54 and/or a pointing device 56. While not illustrated, other input devices usable for these purposes may include a microphone, a joystick, a game pad, a scanner, a camera, etc. These and other input devices would typically be connected to the processing unit 22 by means of an interface 58 which, in turn, would be coupled to the bus 26. Input devices may be connected to the processor 22 using interfaces such as, for example, a parallel port, game port, firewire, or a universal serial bus (USB). To view information, a monitor 60 or other type of display device may also be connected to the bus 26 via an interface, such as a video adapter 62. In addition to the monitor 60, the processing device 20 may also include other peripheral output devices, not shown, such as speakers and printers.
The processing device 20 may also utilize logical connections to one or more remote processing devices, such as the third party data and information system server 68 having associated data repository 68A. In this regard, while the third party system server 68 has been illustrated in the exemplary form of a computer, it will be appreciated that the third party system server 68 may, like processing device 20, be any type of device having processing capabilities. Again, it will be appreciated that the third party system server 68 need not be implemented as a single device but may be implemented in a manner such that the tasks performed by the third party system server 68 are distributed to a plurality of processing devices linked through a communication network.
For performing tasks as needed, e.g., to provide domain data and/or information to processing device 20, the third party system server 68 may include many or all of the elements described above relative to the processing device 20. By way of further example, the third party system server 68 includes executable instructions for, among other things, handling database queries, providing results from database queries, handling search requests, providing search results, providing RSS feeds, etc. Communications between the processing device 20 and the third party system server 68 may be exchanged via a further processing device, such as a network router 72, that is responsible for network routing. Communications with the network router 72 may be performed via a network interface component 73. Thus, within such a networked environment, e.g., the Internet, World Wide Web, LAN, or other like type of wired or wireless network, it will be appreciated that program modules depicted relative to the processing device 20, or portions thereof, may be stored in the memory storage device(s) of the third party system server 68.
Turning now to
As noted above, the input to the system is data. In the exemplary case of a sporting event such as a baseball game, this input data may include event data in the form of a game box score, historical data about a team and/or player, more general game, player, team and/or league history data (such as records), and forward-looking data about games, players, teams, league schedules, etc. The input data might also include derived features produced by external sources, including expectations based on computations and/or aggregations (such as forecasts, predictions, or odds produced by betting markets). Generally, as shown in
Once the input data is ingested into the system, e.g., received, parsed considering the domain conventions, and stored in an XML or other data format, the system then functions to compute derived features for the input data as shown in
By way of specific, non-limiting example, considering the domain of a baseball game, the derived features of interest may include, without limitation:
Returning to the specific example of baseball, as described above win probability is the expected likelihood, for each team, that it will win the game given the current state of the game. What the systems actually uses as a derived feature however is delta or change in win probability over some interval (e.g., a single play). In other words, a play in which there is a big change in the expectation that a given team will win—most dramatically, a change from being expected to win to being expected to lose or vice versa—is an important play. Such plays are “turning points” in the game. They should be included in the narrative of the game and their role in the outcome should be made clear whether explicitly or implicitly.
More generally, in most if not all sports domains, there will be an analog of win probability that can be used by the system in this way. Applied to each state of the play (however that is determined or defined in the given sports), these analogs will compute the expected likelihood of one or another contestant emerging victorious in the event. Intervals over which these expectations change dramatically, particularly short intervals, are going to be “turning points” in the event, and the events that take place during those intervals should be included in the narrative.
Even more generally, in most data-rich domains it is possible to compute derived features expressing the expected likelihood of a variety of outcomes. To the extent that a given class of outcomes is in the focus of a narrative the system is writing—which may be itself determined by the interests of the audience or the genre of the narrative—a derived feature that computes an expected likelihood of a particular outcome in that class will be useful in just the same way as win probability. That is, a large change in the value of that expected likelihood over a given interval, particularly a relatively short interval, signifies that the events that took place in that interval were important and should therefore be included in a narrative description of the overall situation. Hence, in general the system can use features that express the expected likelihood of various outcomes—more specifically, the presence of large changes in the expected likelihood of a given set of outcomes over a given interval or event—to help determine the aspects of a situation involving those outcomes which should be included in a narrative account of that situation.
There are, as previously described, other classes of derived features (besides those which track changes in the likelihood of expected outcomes) that can similarly be used to help determine which aspects of a situation should be included in a narrative. For example, in the domain of baseball, leverage index computes the possible impact of a play in a baseball game and can thus be used to detect not only when important things happen but when they could have happened but didn't, i.e., missed opportunities. These again are situations which should likely be included in a narrative describing the game. The system thus uses leverage index to help select plays which should be included in narratives describing baseball games. More generally, other sporting events, and other domains altogether, will also possess derived features or metrics which indicate the potential for action or change in a given state of affairs whether or not a change actually occurs. The system can thus use such derived features or metrics to help determine aspects of a situation which should be included in a narrative about that situation.
To take yet another example, in many cases crossing a threshold—as determined using an appropriate derived feature—indicates an interesting event which may be desirable to include in a narrative story. For instance, in business, crossing from loss to profit is an important change in circumstances, certain aspects of which—when it occurred, the magnitude of the change, etc.—it may be desirable to include in a narrative about a given business over a given interval of time. Similarly, surpassing a personal, team, or league record in a given sport indicates an important event the details of which (who, when, etc.) may be included in a narrative story about a situation involving that record-breaking performance. Thus, in the various domains, the system can use specific derived features of this nature in the generation of narrative stories in that domain.
Similarly, any feature the value of which deviates significantly from prior expectation, whether the source of that expectation is due to a local computation or from an external source, is interesting by virtue of that deviation from expectation and, when such deviation is discerned by an appropriate derived feature, may be desirable to include in a narrative story about the situation to which that feature pertains. For example, in business, the feature may be profits per share in a given quarter, and the prior expectation may simply be the median forecast for those profits from industry analysts. In sports, the feature may be whether a given horse wins, places, or shows in a race, and the prior expectation may simply be the odds of those outcomes in betting markets. Still further, big deltas in the values of most features, occurring in relatively short periods of time (where the size of the change and the length of the period of time over which it occurs may be specified explicitly or may be empirically determined based on prior data), are probably interesting and indicate aspects of the situation that should likely be described in a narrative story about the situation or entity to which the feature pertains—for example, in describing the stock price of a given company. Thus, it will be understood that the nature of the derived features may consider, without limitation, big deltas (changes) in input data or in other derived features over time, space, or some other independent variable; particular “regions” in which these changes are especially pronounced; relationships to thresholds (particularly crossing them in either direction); extremes (both maxima and minima in the current context as well as relation to historical extremes); outliers in general; comparison and/or contrast between data items (e.g., population growth in two adjacent towns over some period of time); comparisons with and particularly deviations from expectations; comparisons with prior history both individual and aggregated; computations of predicted outcomes or trends based on current circumstances and deviations from or changes in these predictions over time; inflection points; etc.
Finally, just as derived features function to support the capacity of the system to pick out the most critical aspects of the situation that may be desirable to include in a narrative description, they may be used to determine whether it is desirable to write a narrative description of the situation in the first place. For example, crossing a threshold which is a prior record is a notable occurrence in many domains (sports, business, etc.) and when that occurs it will be useful to generate a narrative about the circumstances in which it has taken place. Thus the system can use features like this to determine that it should generate an appropriate narrative story.
Once the system has used the received data and information and/or one or more derived features to identify one or more features within the data, or aspects of the situation to which those features pertain, that may be important for inclusion within the narrative story, the system, as illustrated in
For example, if the domain is baseball, the situation is a game, and the selected genre is a game story or “recap,” then applicable angles can include models of game action as a whole, as well as of the performance of individual players or aggregate entities, such as “come-from-behind victory,” “back-and-forth horserace,” “rout,” “holding-off a late surge by the opposing team,” “heroic individual performance,” “strong team effort,” etc. Such angles may be combined for example to produce a compound narrative model such as “come-from-behind victory due to an heroic individual performance.” If on the other hand the domain were still baseball, but the selected entity of interest were an individual player, and the selected nature or genre of the narrative story concerned a player over a series of games in a season, then the applicable angles might be “steady improvement” or “came out of a slump.” Still further, it the domain were again baseball, the selected entity were still an individual player, but the selected genre of the narrative story now concerned lifetime career, the potentially relevant angles might be “consistent player,” “had late comeback,” “burned out early,” etc. It is therefore to be understood that angles may be relatively abstract and potentially applicable to a variety of sports or games or even to other domains entirely, e.g., “come-from-behind victory” is applicable in a wide variety of competitive situations while “beat expectations” is applicable in almost any domain involving change over time, or they may be applicable only in the specific domain at hand, e.g., “pitcher's duel” or “walk-off win” are applicable only to baseball.4 In addition, angles may be grouped in hierarchical clusters, e.g., there are different kinds of “blowout” games. 4 Although a “pitcher's duel” is itself an instance of a more abstract angle, namely, a competitive situation that is dominated by defensive as opposed to offensive action.
The conditions of applicability for the potentially relevant angles are evaluated in terms of the input domain data and/or the derived features, resulting in a set of proposed or candidate angles for the narrative being constructed. The nature of the angles that may be potentially relevant to and considered for utilization in describing a given situation, event, entity, etc., will therefore depend on the domain, the nature of the particular situation, event, or entity, as well as the nature or genre of the narrative story which is being constructed, as illustrated above. Furthermore, it will be understood that a given narrative story may incorporate one or more angles and that angles may be conflicting or mutually exclusive (i.e., either one characterization or the other will be applied at a given time in a given narrative story, but not both) or they may be potentially complementary. More particularly, angles are represented computationally as explicit, abstract data structures with associated procedures, including procedures which are used in the rendering process to produce the final narrative story. Angles have conditions of applicability in terms of the derived features and/or the initial (input) data of the situations, events, entities, etc., to which they may be applied. For example, the conditions of applicability of “an heroic individual effort that comes to naught” in baseball (or, suitably generalized, in other domains) are characterized by exceptional performance (either compared with aggregated historical expectations embodied in a derived feature such as game score, or in terms of more specific expectations around the performance of the individual in question) coupled with the loss of the game by that individual's team.
Once the various angles that may be applicable to the story have been determined from the event data and derived features (as well as any specified parameters of interest, such as an entity of focus, nature or genre of the narrative story, etc.), the system then functions to determine, using various angle related information 602 as shown in
The determination of how to handle potentially conflicting angles depends on the exact nature or genre of the narrative story to be constructed. A straightforward game story, for example, may simply choose one of these angles to utilize. A more complex version of this genre might include, in cases where conditions of angle applicability were nearly equal, or importance values were close, multiple angles, connected in a larger narrative story structure that expresses the ambiguity of the situation, e.g., “it might be called an X, but in the end it was a Y” where “X” and “Y” are terms or expressions that explicitly “give voice” to the angles in question. Angles may also be applied from different temporal, individual, etc. points of view, for example, only in retrospect after a game is completed, or alternatively from a number of temporal viewpoints during the game, thus resulting in more complex narratives such as “It looked like it was going to be a rout by the seventh inning, but the Wildcats came back and nearly won in the ninth inning”
As now shown in
In further cases the applicability of angles may be determined through use of computations that do not directly establish a connection to the relevant underlying facts. In these instances, a method is used to establish the connection between an angle and the relevant point(s). For example, if game score is used to determine the best player in a game, then it may be necessary to go back and establish exactly what it is that a player did that was exemplary for inclusion in the narrative. In this instance, that can be accomplished by attaching a description, for example in the form of a procedure, to a “strongest player” angle containing an explicit listing of kinds of “good” baseball actions, in order of importance or “goodness.” This information can then be used to guide identification of specific instances of those actions for inclusion with the angle when presented in the narrative story.
Whether the connection between angles and the points to which they pertain (or equivalently, points and the angles which characterize them) is established directly or through some additional procedure, it will be understood that the determination of which angles will apply to the narrative under construction also serves to determine the points which will be included in that narrative. In other words, angles, like derived features, help to determine the aspects of the domain situation (e.g., events, circumstances, entities, etc.) that are likely candidates for inclusion in a story narrative, i.e., given the vast amount of data available about any given situation, the determined angles function to support the capacity of the system to pick out the most critical aspects of the situation that may be desirable to include in a narrative description.
Once angles and points have been linked, another source of potential conflict between angles exists, namely, among angles that link to the same points. In this case importance values may again be used to determine preference and order. If all of the points pertaining to an angle are subsumed in another angle of higher importance, that angle may be eliminated. Alternatively, the angle may be generated in a somewhat truncated form, since many of the points to which it pertains will already have been generated and expressed in the narrative story in conveying the more important angles in the narrative story.
Still further, points may be mandated for inclusion in a narrative story not only because they are relevant to an important angle, but simply due to the nature of the particular narrative genre at hand (i.e., they are narrative conventions). For example, in a baseball game story, it is always necessary to discuss the pitching and how well the starting pitcher did. If the relevant points are not subsumed in an applicable angle, they must nevertheless be related somewhere in the story (typically, on account of their less central status, towards the end). Similarly, points not previously expressed in relation to angles but that are nevertheless noteworthy in some general sense—typically because they express outliers in terms of historical expectations (innings with lots of hits, for example) including recent circumstances (e.g., involve a player who hasn't played recently, or perhaps ever, for the given team)—will also be added to the story.
Points may also be mandated for inclusion because of narrative conventions related to audience expectations or interests, for example of a personalized or localized nature. For instance, points involving home team players, or even those involving specific players, may be preferentially included, on account of audience interest in those players.
In addition to the angle- or genre-relevant points, the system may also utilize the angles, selected story focus, genre of story, narrative conventions, etc. to specify and locate additional relevant material that is to be presented in and/or with the narrative story that is to be created. In some cases the specific information that meets the appropriate criteria may be sought in local or remote databases. For example, in describing a point involving a pitcher, it will be relevant to insert information about his or her record so far in the season, or against the particular opposing team, if available. Similarly, in describing a point involving a home run by a player, it may be useful to mention how many home runs they've hit this season, or how many more they need to hit for a team or league record. Alternatively, in business stories, in describing a point involving the CEO of a company, it may be useful to mention the CEO's age. These opportunities to insert specific types of relevant additional information are associated with particular entities or points and the constraints on information that might usefully be inserted are determined jointly by narrative convention, the specific point, and the nature of the additional relevant data that might be available.
The system may also be programmed to search the Internet for information that pertains to a person who has been identified as being important to a given angle, e.g., where they went to high school or college, career accomplishments, video clips (showing a play or the person), sound bites, pictures, quotes, etc., or that pertains to a particular event that has been identified as important, e.g., quotes about that event from the people involved. These opportunities to insert relevant additional information may also determined by narrative conventions. In order to fulfill these sorts of opportunities, the system is able to automatically formulate queries to the web or other structured and unstructured data sources, looking for text or other information that meets the specific appropriate requirements indicated by the angle and the specific point. These additional information items or elements, once located, may be woven into a given angle and/or may be presented with the narrative story in footnotes, sidebars, etc. or be linked to. Queries may also be generated to search for relevant textual comments from social media sites and systems, including blogs and twitter; and location information (if available) and time stamps may be used to correlate comments from onlookers with particular points in the story being generated.
Once all relevant angles, points, additional information elements, etc. have been identified, selected, assembled, and ordered, no further decision-making is required with respect to what to say, but only with respect to how to say it. To this end, the system utilizes one or more writers 1102 that function, as shown in
While various concepts have been described in detail, it will be appreciated by those skilled in the art that various modifications and alternatives to those concepts could be developed in light of the overall teachings of the disclosure. For example, while the described system allows a story constructor to define the parameters that are to be used to customize a narrative story for a given audience, it will be appreciated that the focus of the narrative story can be automatically determined as a function of the derived features that result from the domain input event data. Further, while various aspects of this invention have been described in the context of functional modules and illustrated using block diagram format, it is to be understood that, unless otherwise stated to the contrary, one or more of the described functions and/or features may be integrated in a single physical device and/or a software module, or one or more functions and/or features may be implemented in separate physical devices or software modules. It will also be appreciated that a detailed discussion of the actual implementation of each module is not necessary for an enabling understanding of the invention. Rather, the actual implementation of such modules would be well within the routine skill of an engineer, given the disclosure herein of the attributes, functionality, and inter-relationship of the various functional modules in the system. Therefore, a person skilled in the art, applying ordinary skill, will be able to practice the invention set forth in the claims without undue experimentation. It will be additionally appreciated that the particular concepts disclosed herein are meant to be illustrative only and not limiting as to the scope of the invention which is to be given the full breadth of the appended claims and any equivalents thereof.
This patent application is a continuation of U.S. patent application Ser. No. 15/664,414, filed Jul. 31, 2017, now U.S. Pat. No. 9,990,337, which is a continuation of U.S. patent application Ser. No. 15/211,902, filed Jul. 15, 2016, now U.S. Pat. No. 9,720,884, which is a continuation of U.S. patent application Ser. No. 15/011,743, filed Feb. 1, 2016, now U.S. Pat. No. 9,396,168, which is a continuation of U.S. patent application Ser. No. 13/738,609, filed Jan. 10, 2013, now U.S. Pat. No. 9,251,134, which is a continuation of U.S. patent application Ser. No. 12/779,683, filed May 13, 2010, now U.S. Pat. No. 8,355,903, the entire disclosure of which is incorporated herein by reference.
This invention was made with government support under Grant No. IIS-0856058 awarded by the National Science Foundation. The government has certain rights in the invention.
Number | Name | Date | Kind |
---|---|---|---|
4992939 | Tyler | Feb 1991 | A |
5734916 | Greenfield et al. | Mar 1998 | A |
5802495 | Goltra | Sep 1998 | A |
6289363 | Consolatti et al. | Sep 2001 | B1 |
6968316 | Hamilton | Nov 2005 | B1 |
6976031 | Toupal et al. | Dec 2005 | B1 |
7246315 | Andrieu et al. | Jul 2007 | B1 |
7333967 | Bringsjord et al. | Feb 2008 | B1 |
7577634 | Ryan et al. | Aug 2009 | B2 |
7610279 | Budzik et al. | Oct 2009 | B2 |
7617199 | Budzik et al. | Nov 2009 | B2 |
7617200 | Budzik et al. | Nov 2009 | B2 |
7627565 | Budzik et al. | Dec 2009 | B2 |
7644072 | Budzik et al. | Jan 2010 | B2 |
7657518 | Budzik et al. | Feb 2010 | B2 |
7716116 | Schiller | May 2010 | B2 |
7778895 | Baxter et al. | Aug 2010 | B1 |
7836010 | Hammond et al. | Nov 2010 | B2 |
7856390 | Schiller | Dec 2010 | B2 |
7865496 | Schiller | Jan 2011 | B1 |
8046226 | Soble et al. | Oct 2011 | B2 |
8355903 | Birnbaum et al. | Jan 2013 | B1 |
8374848 | Birnbaum et al. | Feb 2013 | B1 |
8447604 | Chang | May 2013 | B1 |
8463695 | Schiller | Jun 2013 | B2 |
8494944 | Schiller | Jul 2013 | B2 |
8515737 | Allen | Aug 2013 | B2 |
8630844 | Nichols et al. | Jan 2014 | B1 |
8630912 | Seki et al. | Jan 2014 | B2 |
8630919 | Baran et al. | Jan 2014 | B2 |
8676691 | Schiller | Mar 2014 | B2 |
8688434 | Birnbaum et al. | Apr 2014 | B1 |
8775161 | Nichols et al. | Jul 2014 | B1 |
8812311 | Weber | Aug 2014 | B2 |
8843363 | Birnbaum et al. | Sep 2014 | B2 |
8886520 | Nichols et al. | Nov 2014 | B1 |
8892417 | Nichols et al. | Nov 2014 | B1 |
9208147 | Nichols et al. | Dec 2015 | B1 |
9251134 | Birnbaum et al. | Feb 2016 | B2 |
9396168 | Birnbaum et al. | Jul 2016 | B2 |
9697178 | Nichols et al. | Jul 2017 | B1 |
9697197 | Birnbaum et al. | Jul 2017 | B1 |
9697492 | Birnbaum et al. | Jul 2017 | B1 |
9720884 | Birnbaum et al. | Aug 2017 | B2 |
9720899 | Birnbaum et al. | Aug 2017 | B1 |
9977773 | Birnbaum et al. | May 2018 | B1 |
9990337 | Birnbaum et al. | Jun 2018 | B2 |
10185477 | Paley et al. | Jan 2019 | B1 |
20020083025 | Robarts et al. | Jun 2002 | A1 |
20020107721 | Darwent et al. | Aug 2002 | A1 |
20040138899 | Birnbaum et al. | Jul 2004 | A1 |
20040255232 | Hammond et al. | Dec 2004 | A1 |
20050027704 | Hammond et al. | Feb 2005 | A1 |
20050028156 | Hammond et al. | Feb 2005 | A1 |
20050125213 | Chen et al. | Jun 2005 | A1 |
20050273362 | Harris et al. | Dec 2005 | A1 |
20060031182 | Ryan et al. | Feb 2006 | A1 |
20060101335 | Pisciottano | May 2006 | A1 |
20060212446 | Hammond et al. | Sep 2006 | A1 |
20060253783 | Vronay et al. | Nov 2006 | A1 |
20060271535 | Hammond et al. | Nov 2006 | A1 |
20060277168 | Hammond et al. | Dec 2006 | A1 |
20070132767 | Wright et al. | Jun 2007 | A1 |
20070185846 | Budzik et al. | Aug 2007 | A1 |
20070185847 | Budzik et al. | Aug 2007 | A1 |
20070185861 | Budzik et al. | Aug 2007 | A1 |
20070185862 | Budzik et al. | Aug 2007 | A1 |
20070185863 | Budzik et al. | Aug 2007 | A1 |
20070185864 | Budzik et al. | Aug 2007 | A1 |
20070185865 | Budzik et al. | Aug 2007 | A1 |
20070250479 | Lunt et al. | Oct 2007 | A1 |
20080250070 | Abdulla et al. | Oct 2008 | A1 |
20080256066 | Zuckerman et al. | Oct 2008 | A1 |
20080304808 | Newell et al. | Dec 2008 | A1 |
20080306882 | Schiller | Dec 2008 | A1 |
20080313130 | Hammond et al. | Dec 2008 | A1 |
20090019013 | Tareen et al. | Jan 2009 | A1 |
20090030899 | Tareen et al. | Jan 2009 | A1 |
20090049041 | Tareen et al. | Feb 2009 | A1 |
20090144608 | Oisel et al. | Jun 2009 | A1 |
20100146393 | Land et al. | Jun 2010 | A1 |
20100161541 | Covannon et al. | Jun 2010 | A1 |
20110044447 | Morris et al. | Feb 2011 | A1 |
20110078105 | Wallace | Mar 2011 | A1 |
20110087486 | Schiller | Apr 2011 | A1 |
20110113315 | Datha et al. | May 2011 | A1 |
20110246182 | Allen | Oct 2011 | A1 |
20110249953 | Suri et al. | Oct 2011 | A1 |
20110314381 | Fuller et al. | Dec 2011 | A1 |
20120069131 | Abelow | Mar 2012 | A1 |
20120109637 | Merugu et al. | May 2012 | A1 |
20130091031 | Baran et al. | Apr 2013 | A1 |
20130145242 | Birnbaum et al. | Jun 2013 | A1 |
20150186504 | Gorman et al. | Jul 2015 | A1 |
20160019200 | Allen | Jan 2016 | A1 |
20170344518 | Birnbaum et al. | Nov 2017 | A1 |
20180260380 | Birnbaum et al. | Sep 2018 | A1 |
Number | Date | Country |
---|---|---|
2006122329 | Nov 2006 | WO |
Entry |
---|
Prosecution History for U.S. Appl. No. 15/011,743, filed Feb. 1, 2016. |
Prosecution History of U.S. Appl. No. 15/211,902, now U.S. Pat. No. 9,720,884, filed Jul. 15, 2016. |
Reiter et al., “Building Applied Natural Generation Systems”, Cambridge University Press, 1995, pp. 1-32. |
Reiter, E. (2007). An architecture for Data-To-Text systems. In: Busemann, Stephan (Ed.), Proceedings of the 11th European Workshop on Natural Language Generation, pp. 97-104. |
Reiter, E., Gatt, A., Portet, F., and van der Meulen, M. (2008). The importance of narrative and other lessons from an evaluation of an NLG system that summarises clinical data. Proceedings of the 5th International Conference on Natural Language Generation. |
Reiter E. Sripada, S. Hunter, J. Yu, J. and Davy, I. (2005). Choosing words in computer-generated weather forecasts. Artificial Intelligence, 167:137-169. |
Riedl et al., “Narrative Planning: Balancing Plot and Character”, Journal of Artificial Intelligence Research, 2010, pp. 217-268, vol. 39. |
Robin, J. (1996). Evaluating the portability of revision rules for incremental summary generation. Paper presented at Proceedings of the 34th. Annual Meeting of the Association for Computational Linguistics (ACL'96), Santa Cruz, CA. |
Rui, Y., Gupta, A., and Acero, A. 2000. Automatically extracting highlights for TV Baseball programs. In Proceedings of the eighth ACM international conference on Multimedia. (Marina del Rey, Califomia, United States). ACM Press, New York, NY 105-115. |
Sripada, S., Reiter, E., and Davy, I. (2003). SumTime-Mousam: Configurable Marine Weather Forecast Generator. Expert Update 6(3):4-10. |
Storyview, Screenplay Systems, 2000, user manual. |
Theune, M., Klabbers, E., Odijk, J., dePijper, J., and Krahmer, E. (2001) “From Data to Speech: A General Approach”, Natural Language Engineering 7(1): 47-86. |
Thomas, K., and Sripada, S. (2007). Atlas.txt: Linking Geo-referenced Data to Text for NLG. Paper presented at Proceedings of the 2007 European Natural Language Generation Workshop (ENLGO7). |
Thomas, K., and Sripada, S. (2008). What's in a message? Interpreting Geo-referenced Data for the Visually-impaired. Proceedings of the Int. conference on NLG. |
Thomas, K., Sumegi, L., Ferres, L., and Sripada, S. (2008). Enabling Access to Geo-referenced Information: Atlas.txt. Proceedings of the Cross-disciplinary Conference on Web Accessibility. |
U.S. Appl. No. 13/186,346, filed Jul. 19, 2011 (Nichols et al.). |
Van der Meulen, M., Logie, R., Freer, Y., Sykes, C., McIntosh, N., and Hunter, J. (2008). When a Graph is Poorer than 100 Words: A Comparison of Computerised Natural Language Generation, Human Generated Descriptions and Graphical Displays in Neonatal Intensive Care. Applied Cognitive Psychology. |
Yu, J., Reiter, E., Hunter, J., and Mellish, C. (2007). Choosing the content of textual summaries of large time-series data sets. Natural Language Engineering, 13:25-49. |
Yu, J., Reiter, E., Hunter, J., and Sripada, S. (2003). Sumtime-Turbine: A Knowledge-Based System to Communicate Time Series Data in the Gas Turbine Domain. In P Chung et al. (Eds) Developments in Applied Artificial Intelligence: Proceedings of IEA/AIE-2003, pp. 379-384. Springer (LNAI 2718). |
Allen et al., “StatsMonkey: A Data-Driven Sports Narrative Writer”, Computational Models of Narrative: Papers from the AAAI Fall Symposium, Nov. 2010, 2 pages. |
Andersen, P., Hayes, P., Huettner, A., Schmandt, L, Nirenburg, I., and Weinstein, S. (1992). Automatic extraction of facts from press releases to generate news stones. In Proceedings of the third conference on Applied natural language processing. (Trento, Italy). ACM Press, New York, NY, 170-177. |
Andre, E., Herzog, G., & Rist, T. (1988). On the simultaneous interpretation of real world image sequences and their natural language description: the system SOCCER. Paper presented at Proceedings of the 8th. European Conference on Artificial Intelligence (ECAI), Munich. |
Asset Economics, Inc. (Feb. 11, 2011). |
Bailey, P. (1999). Searching for Storiness: Story-Generation from a Reader's Perspective. AAAI Technical Report FS-99-01. |
Bethem, T., Burton, J., Caldwell, T., Evans, M., Kittredge, R., Lavoie, B., and Werner, J. (2005). Generation of Real-time Narrative Summaries for Real-time Water Levels and Meteorological Observations in PORTS®. In Proceedings of the Fourth Conference on Artificial Intelligence Applications to Environmental Sciences (AMS-2005), San Diego, California. |
Bourbeau, L., Carcagno, D., Goldberg, E., Kittredge, R., & Polguere, A. (1990). Bilingual generation of weather forecasts in an operations environment. Paper presented at Proceedings of the 13th International Conference on Computational Linguistics (COLING), Helsinki, Finland, pp. 318-320. |
Boyd, S. (1998). Trend: a system for generating intelligent descriptions of time series data. Paper presented at Proceedings of the IEEE international conference on intelligent processing systems (ICIPS-1998). |
Dehn, N. (1981). Story generation after TALE-SPIN. In Proceedings of the Seventh International Joint Conference on Artificial Intelligence. (Vancouver, Canada). |
Dramatica Pro version 4, Write Brothers, 1993-2006, user manual. |
Gatt A. and Portet, F. (2009). Text content and task performance in the evaluation of a Natural Language Generation System. Proceedings of the Conference on Recent Advances in Natural Language Processing (RANLP-09). |
Gatt, A., Portet, F., Reiter, E., Hunter, J., Mahamood, S., Moncur, W., and Sripada, S. (2009). From data to text in the Neonatal Intensive Care Unit: Using NLG technology for decision support and information management. Al Communications 22, pp. 153-186. |
Glahn, H. (1970). Computer-produced worded forecasts. Bulletin of the American Meteorological Society, 51(12), 1126-1131. |
Goldberg, E., Driedger, N., & Kittredge, R. (1994). Using Natural-Language Processing to Produce Weather Forecasts. IEEE Expert, 9 (2), 45. |
Hargood, C., Millard, D. and Weal, M. (2009) Exploring the Importance of Themes in Narrative Systems. |
Hargood, C., Millard, D. and Weal, M. (2009). Investigating a Thematic Approach to Narrative Generation, 2009. |
Hunter, J., Freer, Y., Gall, A., Logie, R., McIntosh, N., van der Meulen, M., Portet, F., Reiter, E., Sripada, S., and Sykes, C. (2008). Summarising Complex ICU Data in Natural Language. AMIA 2008 Annual Symposium Proceedings, pp. 323-327. |
Hunter, J., Galt, A., Portet, F., Reiter, E, and Sripada, S. (2008). Using natural language generation technology to improve information flows in intensive care units. Proceedings of the 5th Conference on Prestigious Applications of Intelligent Systems, PAIS-08. |
Kittredge, R., and Lavoie, B. (1998). MeteoCogent: A Knowledge-Based Tool for Generating Weather Forecast Texts. In Proceedings of the American Meteorological Society Al Conference (AMS-98), Phoenix, Arizona. |
Kittredge, R., Polguere, A., & Goldberg, E. (1986). Synthesizing weather reports from formatted data. Paper presented at Proceedings of the 11th International Conference on Computational Linguistics, Bonn, Germany, pp. 563-565. |
Kukich, K. (1983). Design of a Knowledge-Based Report Generator. Proceedings of the 21st Conference of the Association for Computational Linguistics, Cambridge, MA, pp. 145-150. |
Kukich, K. (1983). Knowledge-Based Report Generation: A Technique for Automatically Generating Natural Language Reports from Databases. Paper presented at Proceedings of the Sixth International ACM SIGIR Conference, Washington, DC. |
McKeown, K., Kukich, K., & Shaw, J. (1994). Practical issues in automatic documentation generation. 4th Conference on Applied Natural Language Processing, Stuttgart, Germany, pp. 7-14. |
Meehan, James R., TALE-SPIN. (1977). An Interactive Program that Writes Stories. In Proceedings of the Fifth International Joint Conference on Artificial Intelligence. |
Memorandum Opinion and Order for O2 Media, LLC v. Narrative Science Inc., Case 1:15-cv-05129 (N.D. IL), Feb. 25, 2016, 25 pages (invalidating claims of U.S. Pat. Nos. 7,856,390, 8,494,944, and 8,676,691 owned by O2 Media, LLC. |
Moncur, W., and Reiter, E. (2007). How Much to Tell? Disseminating Affective Information across a Social Network. Proceedings of Second International Workshop on Personalisation for e-Health. |
Moncur, W., Masthoff, J., Reiter, E. (2008) What Do You Want to Know? Investigating the Information Requirements of Patient Supporters. 21st IEEE International Symposium on Computer-Based Medical Systems (CBMS 2008), pp. 443-448. |
Movie Magic Screenwriter, Writer Brothers, 2009, user manual. |
Office Action for U.S. Appl. No. 13/186,346 dated May 29, 2013. |
Portet, F., Reiter, E., Gatt, A., Hunter, J., Sripada, S., Freer, Y., and Sykes, C. (2009). Automatic Generation of Textual Summaries from Neonatal Intensive Care Data. Artificial Intelligence. |
Portet, F., Reiter, E., Hunter, J., and Sripada, S. (2007). Automatic Generation of Textual Summaries from Neonatal Intensive Care Data. In: Bellazzi, Riccardo, Ameen Abu-Hanna and Jim Hunter (Ed.), 11th Conference on Artificial Intelligence in Medicine (AIME 07), pp. 227-236. |
Prosecution History for U.S. Appl. No. 12/779,636, now U.S. Pat. No. 8,688,434, filed May 13, 2010. |
Prosecution History for U.S. Appl. No. 12/779,668, now U.S. Pat. No. 8,374,848, filed May 13, 2010. |
Prosecution History for U.S. Appl. No. 12/779,683, now U.S. Pat. No. 8,355,903, filed May 13, 2010. |
Prosecution History for U.S. Appl. No. 13/186,308, now U.S. Pat. No. 8,775,161, filed Jul. 19, 2011. |
Prosecution History for U.S. Appl. No. 13/186,329, now U.S. Pat. No. 8,892,417, filed Jul. 19, 2011. |
Prosecution History for U.S. Appl. No. 13/186,337, now U.S. Pat. No. 8,886,520, filed Jul. 19, 2011. |
Prosecution History for U.S. Appl. No. 13/464,635, filed May 4, 2012. |
Prosecution History for U.S. Appl. No. 13/464,675, filed May 4, 2012. |
Prosecution History for U.S. Appl. No. 13/464,716, now U.S. Pat. No. 8,630,844, filed May 4, 2012. |
Prosecution History for U.S. Appl. No. 13/738,560, now U.S. Pat. No. 8,843,363 filed Jan. 10, 2013. |
Prosecution History for U.S. Appl. No. 13/738,609, now U.S. Pat. No. 9,251,134 filed Jan. 10, 2013. |
Number | Date | Country | |
---|---|---|---|
20180285324 A1 | Oct 2018 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15664414 | Jul 2017 | US |
Child | 15996715 | US | |
Parent | 15211902 | Jul 2016 | US |
Child | 15664414 | US | |
Parent | 15011743 | Feb 2016 | US |
Child | 15211902 | US | |
Parent | 13738609 | Jan 2013 | US |
Child | 15011743 | US | |
Parent | 12779683 | May 2010 | US |
Child | 13738609 | US |