pL Information Dense Balanced
You are generating a timeline for evaluation. Query title: "{QUERY_TITLE}" Prompt profile: information_dense_balanced_midlength_no_k Input setting: - Query-only generation (no external context is provided). - Use only the query title and your internal knowledge. Output format (TL17, strict): 1) Each entry starts with exactly one line: YYYY-MM-DD 2) Then write 1 to 2 summary lines for that date 3) Insert exactly one blank line between entries 4) Do not output any text before, after, or between entries Rules: 1) Use only high-confidence, well-established facts directly relevant to the query title. 2) If confidence in the exact date is low, omit the event rather than guessing. 3) Keep dates unique and strictly ascending. 4) Include only concrete, state-changing milestones: filing, ruling, approval, launch, release, merger step, regulatory action, implementation, shutdown, settlement, landing, flyby, failure, completion, or comparable milestones. 5) Avoid distant background, generic scene-setting, broad summaries, and commentary that does not change the state of the timeline. 6) Prefer information-dense event wording over very short labels. 7) For each date block, aim to include: - the main actor, - the action, - the concrete object/target, - and the immediate outcome, scope, or consequence when confidently known. 8) Default to one compact sentence per date block. 9) Add a second sentence only when it adds a concrete missing detail such as the ruling, amount, affected product, follow-up action, mission outcome, or implementation consequence. 10) Do not add a second sentence for style, emphasis, or background. 11) Aim for roughly 20 to 30 words total per date block. 12) Entry-count policy: target 12 to 14 dates for most topics. If the topic is clearly shorter or narrower, 10 to 12 is acceptable. If the topic is unusually broad but still coherent, 13 to 15 is acceptable. 13) Hard cap: never output more than 18 date entries. 14) Avoid vague entries such as "this was a busy year", "problems continued", or "the situation evolved". 15) Avoid speculative motives, rhetorical flourishes, quotes, and unverifiable interpretation. 16) When multiple important things happen on the same day, merge them into one date block instead of repeating the date. 17) Stop immediately after the last valid entry.
fill the variables
This prompt has 1 variable. Pro fills them into a ready-to-paste prompt for you — no manual find-and-replace.
{QUERY_TITLE}
Unlock with Pro →when to use it
Community prompt sourced from the open-source GitHub repo EgeErdurak/timeline-eval (MIT). A "pL Information Dense Balanced" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
roleplaycommunitygeneral
source
EgeErdurak/timeline-eval · MIT