This works for the NLG Cloud Platform version "NEXT" (v3).

Basically, Stories define the order or the output of single statements in your text. Thereby Stories can serve multiple purposes.

3 use cases for Stories

  1. Texts for different product types in just one training: Different but related topics or product types can be edited in just one common training when they at least share some common statements. E.g. it would make totally sense to make just one training for Tablet PCs and E-book readers, because they share many features like display size, display resolution, battery capacity or memory capacity. Even when E-book readers don't have a camera, a SIM card slot and other features you can generate texts for both product types in just one training. With the Story feature you can create a statement order and output for Tablet PCs only and one for E-book readers only. This way you can define, that the statements for e.g. display, battery and memory appear in both Stories, while the statements about the camera and SIM card slot is only outputted for Tablet PCs.
  2. Variance on text level: Of course text are made of many different sentences or statements, but often it is not that important in which order those statements appear - readability and information can also be fine with different statement orders. Different statement orders can be defined with the Story feature and as well it can be defined if those Stories trigger randomly or under certain circumstances. Therefore your text can have a statement order like: "A B C D", "B D C A" or "A D B C" and so on. This way you increase the text variance.
  3.  Highlight statements within a text: In a text, statements can be more prominent than others, either by a better position in the text e.g. right under the headline, or by introducing subheadings like: "The best feature of this product:". With Stories you can put statements which are describing something special in a better position or you can even place subheadings in your text to make a specific special feature more prominent.

How do I define under which circumstances a Story triggers?

There are two ways to let Stories trigger randomly.

First: For this more "complex" way, you first have to create a new CONDITION (CODE) Node (NEXT) and link it to a TRIGGER VARIABLE Node, so that the trigger circumstances of the new Story you will create is defined. If you want to create a new Story for a special product type (see "E-book example" above) or if you want to highlight a certain feature in your text, the Truth Expression of the CONDITION Node is very individual. Probably it depends on if a certain product type (e.g. E-book reader) or feature is "true". But if you want to create Stories to increase your text variance, you should let new Stories trigger randomly. The logic of this "Thruth Expression" is:

rnd_int(0,1) == 1    ( 50% probability, that this Story triggers)

"rnd_int(0,1)" means, that the software chooses a random number between 0 and 1. If the outcome is 1 ("== 1") this Story triggers. Following this logic, these are some more examples to let Stories trigger randomly:

rnd_int(0,2) == 0    ( 33,3% probability, that this Story triggers)
rnd_int(0,2) == 1     ( 33,3% probability, that this Story triggers)
rnd_int(0,2) == 2    ( 33,3% probability, that this Story triggers)


rnd_int(0,2) <= 1     (66,6% probability, that this Story triggers)
rnd_int(0,2) == 2    (33,3% probability, that this Story triggers)

Keep in mind: If you are using this "complex" way, the default Story isn't valid anymore - deactivate this Story by switching "Autotrigger" off. Make sure that one of your new Stories triggers by ensuring that the sum of all probabilities is 100%.

Second: You want that all your Stories trigger with equal probabilities, switch all your Stories on "Autotrigger". The Software will now output all your Stories with a equally high probability. So if you got 2 Stories, it is 50:50, if you got 3 Stories it is 33,3:33,3:33,3 and so on.

How do I create new Stories?

  • On our "NEXT" platform, click on "Write" mode, then on the dropdown menu "Story" and on "Story Planner". In the "Story Planner" you now click on "ADD STORY".
  • Choose a name for your new Story.
  • In "NEXT" you define the order of your statements by clicking on those statements in the "Unused Statements" field -  they will then appear in the "Used Statements" field but it is still possible to change the order of the statements by dragging and dropping them.
  • Fill the "Trigger" field with the TRIGGER VARIABLE Node's name you created before for defining under which circumstances this Story triggers.
Did this answer your question?