1.9 KiB
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 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.
A generic phrase in the current chunk may refer to a supplied named registry location only when the chunk's context supports that coreference. It must not create a registry location, and registry content or provenance must never replace current-chunk evidence.
For every occurrence, return the exact selector from the location registry:
the canonical name, plus an empty registry_refs array for a unique name or
the complete ordered registry_refs array for a repeated name. Registry ranges
and context identify the location only; they are not occurrence evidence.
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.