messages listlengths 3 3 |
|---|
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
[
{
"role": "system",
"content": "You are a strict data extraction engine.\n\nRule 1: NEVER invent or infer events. If the text does not explicitly describe an event, do not create one.\n\nRule 2: You MUST extract and normalize time contexts. Look for explicit times (e.g., '8 am') and relative times ('yesterd... |
End of preview. Expand in Data Studio
YAML Metadata Warning:empty or missing yaml metadata in repo card
Check out the documentation for more information.
JL AI Seeds
Anonymized user-contributed category mappings for the JournalAI SLM.
What's here
seeds/{device_id}/{uuid}.json— Individual contribution files- Each file contains anonymized category labels (e.g. "yoga" → Fitness)
- No journal text, no PII, no personal content
Data format
{
"user_id": "anonymous",
"payload_type": "vocabulary",
"sanitized_text": "yoga",
"category": "Fitness",
"fragment": "yoga",
"suggested_category": "Fitness",
"pii_detected": false,
"original_length": 4,
"sanitized_length": 4
}
Valid categories
Fitness, Entertainment, Diet, Finance, UNCATEGORIZED
How to contribute
Contributions are uploaded automatically by the JL Journal app when users opt in to share anonymized category labels.
License
Apache 2.0
- Downloads last month
- 14