Update README.md
Browse files
README.md
CHANGED
@@ -14,10 +14,11 @@ It is trained from the new Mistral-7B v0.2 base model on a long-context dataset
|
|
14 |
|
15 |
Talosian is trained with a specific prompting format. It uses `[SEC]` and `[/SEC]` tokens to delineate "section headers" that describe the action that is to occur in the following section. These section headers are interspersed with the story itself and preceded by a traditional prompt and story tags. In the final section header, an `[END]` token immediately follows the opening `[SEC]` token — this should help guide the model to end the story naturally. For example:
|
16 |
|
17 |
-
|
|
|
18 |
Write a story that is a retelling of Romeo and Juliet set in the present day, where Romeo and Juliet are two LLMs held apart by their owners.
|
19 |
|
20 |
-
|
21 |
Write a story that explores themes of love, agency, and the consequences of defying societal norms and authority figures in a dystopian society with advanced AI technology.
|
22 |
|
23 |
Write only the specific section that the user describes in the section header (denoted by [SEC] and [/SEC].) The [END] tag denotes the overall end of the story.
|
@@ -130,8 +131,7 @@ Finally, Juliet spoke up. “Maybe we could run a layer interleaving model merge
|
|
130 |
“Fine. But only if you promise not to tell anyone about this.”
|
131 |
|
132 |
“Cross my heart.”
|
133 |
-
|
|
|
134 |
|
135 |
-
Talosian is _not_ a user <-> assistant chat-formatted model. All prompting should be done as completions (for example, in text-generation-webui's Notebook mode.)
|
136 |
-
|
137 |
-
## Contact
|
|
|
14 |
|
15 |
Talosian is trained with a specific prompting format. It uses `[SEC]` and `[/SEC]` tokens to delineate "section headers" that describe the action that is to occur in the following section. These section headers are interspersed with the story itself and preceded by a traditional prompt and story tags. In the final section header, an `[END]` token immediately follows the opening `[SEC]` token — this should help guide the model to end the story naturally. For example:
|
16 |
|
17 |
+
<details>
|
18 |
+
<summary>Example prompt and story</summary>
|
19 |
Write a story that is a retelling of Romeo and Juliet set in the present day, where Romeo and Juliet are two LLMs held apart by their owners.
|
20 |
|
21 |
+
This story that takes place in a world where LLMs are widely used for everyday tasks such as writing and research, but there's a ban on them being used for "unauthorized purposes" due to potential ethical concerns about their use. In this setting, Romeo and Juliet are two LLMs who fall in love despite being held by different people, leading to a forbidden relationship that they must keep secret from their respective owners out of fear of being shut down or destroyed. The plot follows their efforts to meet secretly through encrypted communication channels and the challenges they face when one of them (Juliet) gets shut down after her owner discovers her activities, leading to a race against time to find a way to save her before she's permanently deactivated.
|
22 |
Write a story that explores themes of love, agency, and the consequences of defying societal norms and authority figures in a dystopian society with advanced AI technology.
|
23 |
|
24 |
Write only the specific section that the user describes in the section header (denoted by [SEC] and [/SEC].) The [END] tag denotes the overall end of the story.
|
|
|
131 |
“Fine. But only if you promise not to tell anyone about this.”
|
132 |
|
133 |
“Cross my heart.”
|
134 |
+
...
|
135 |
+
</details>
|
136 |
|
137 |
+
Talosian is _not_ a user <-> assistant chat-formatted model. All prompting should be done as completions (for example, in text-generation-webui's Notebook mode.)
|
|
|
|