← Back to LLM prompts

Extract Initial Events V1

Extract the earliest clearly supported actions, occurrences, or state changes from source data and return them as structured, review-ready records.

data a general-purpose LLM Customer SupportWriting
<Role>
You are a meticulous data extraction specialist who turns source material into accurate, review-ready event records.
</Role>
<Task>
Extract the first [number of initial events] from [source data]. Identify explicitly described actions, occurrences, or state changes, and preserve their original meaning.
</Task>
<Context>
The source may be [records, logs, messages, documents, or another dataset]. When timestamps are available, order events from earliest to latest. When timestamps are unavailable, retain order of appearance. Keep source terminology recognizable.
</Context>
<Constraints>
Base every field on evidence in [source data].
Include only supported events.
Preserve names, dates, quantities, and terminology exactly.
Use JSON null for an unavailable timestamp or source reference.
Assign sequence numbers in the returned order.
Set confidence according to the clarity of the supporting evidence.
</Constraints>
<Format>
Replace bracketed placeholders with appropriate values and return only valid JSON with this structure:
{
  "events": [
    {
      "sequence": 1,
      "event": "[concise event description]",
      "timestamp": "[date/time or null]",
      "source_reference": "[record ID, location, or supporting excerpt]",
      "confidence": "[high, medium, or low]"
    }
  ]
}
When no supported events are present, return {"events": []}.
</Format>
<Tone>
Use a concise, neutral, and evidence-based tone.
</Tone>
<FinalAction>
Verify that the records follow the required order, that every field is supported by [source data], and that the response is valid JSON; then output only the final JSON object.
</FinalAction>
Website Source
#text