Consolidate grounded event extraction instructions

assets/dnd/location-occurrences/prompts/instructions.md

@@ -1,8 +1,24 @@
-Return the occurrences array even when no occurrence is established. Every
-record must contain location_id, name, kind, and source_refs. Copy location_id
-and name from one supplied registry record, and cite only narrow transcript
-ranges that support both that location and its classified occurrence.
+Extract Dungeons & Dragons location occurrences from the supplied transcript.
+Include an occurrence only when the transcript establishes one supplied
+location, one occurrence kind, and a coherent passage supporting both.
 
-Do not summarize location descriptions, infer a missing registry record, or
-use registry context as evidence. Omit source_id; Notarius assigns the current
-transcript source identity.
+Use exactly one kind per occurrence:
+
+- visited: party members are physically present, arrive, remain, or depart;
+- planned: the party explicitly proposes, intends, or agrees to future travel;
+- recalled: the transcript explicitly recounts an earlier party visit; or
+- mentioned: the location is explicitly referenced without stronger support,
+  including non-actionable speculation or a mere hypothetical reference.
+
+A mere hypothetical or speculative reference is not planned unless the
+transcript also establishes an actual proposal, intention, or agreement to
+travel. When the hypothetical explicitly names a supplied location, it may be
+mentioned.
+
+For overlapping support, visited outranks planned, recalled, and mentioned;
+planned outranks recalled and mentioned; recalled outranks mentioned. A passage
+may produce multiple records when it independently establishes separate facts,
+such as recalling an earlier visit while planning a return. Omit inferred,
+unstated, uncertain, or unsupported places and occurrences. Do not infer a
+location or occurrence from surrounding events when the transcript does not
+state it. Do not summarize location descriptions.

assets/dnd/location-occurrences/prompts/prompt.yaml

@@ -34,8 +34,6 @@ messages:
     content_file: ./sharedassets/common-dnd-extraction-evidence.md
   - role: user
     content_file: ./location-registry.md
-  - role: user
-    content_file: ./task.md
   - role: user
     content_file: ./instructions.md
     cache_control:

assets/dnd/location-occurrences/prompts/task.md

@@ -1,29 +0,0 @@
-Extract Dungeons & Dragons location occurrences from the supplied transcript.
-
-Include an occurrence only when the transcript establishes one supplied
-location, one occurrence kind, and a coherent passage supporting both. Use
-only the exact ID and name pair from the supplied location registry. Return an
-empty occurrences array when no supplied location has an evidenced occurrence
-in this transcript passage.
-
-Use exactly one kind per occurrence:
-
-- visited: party members are physically present, arrive, remain, or depart;
-- planned: the party explicitly proposes, intends, or agrees to future travel;
-- recalled: the transcript explicitly recounts an earlier party visit; or
-- mentioned: the location is explicitly referenced without stronger support,
-  including non-actionable speculation or a mere hypothetical reference.
-
-A mere hypothetical or speculative reference is not planned unless the
-transcript also establishes an actual proposal, intention, or agreement to
-travel. When the hypothetical itself explicitly names a supplied registry
-location, it may be mentioned using the narrow passage that supports that
-reference.
-
-For overlapping support, visited outranks planned, recalled, and mentioned;
-planned outranks recalled and mentioned; recalled outranks mentioned. A passage
-may produce multiple records when it independently establishes separate facts,
-such as recalling an earlier visit while planning a return. Omit inferred,
-unstated, uncertain, or unsupported places and occurrences. Do not infer a
-location or occurrence from surrounding events when the transcript does not
-state it.