Accept traced entity capture citations and improve correction feedback
This commit is contained in:
1 parent
4c73b00494
commit
12bc84c02c
12 files changed
+2020
-11
No files matched your search
@@ -144,3 +144,30 @@ with package ID `trial-entity-resolution-schema-BUG-000020-20261015`:
|
||||
```powershell
|
||||
.\.venv\Scripts\python.exe -m viano_bug_analysis.trial run --workspace service-data/trials/entity-resolution-schema-20261015 --llm-config config/llm.timeout300.local.toml --project-config config/project.local.toml --case-id BUG-000020 --package-id trial-entity-resolution-schema-BUG-000020-20261015 --stop-after interpretation --max-dispatches 6
|
||||
```
|
||||
|
||||
## Interpretation citation policy v2
|
||||
|
||||
New resolution input artifacts additionally freeze
|
||||
`interpretation_protocol_version = 2`. Their context uses `linked_capture_v2`
|
||||
citation markers and `case_interpretation_resolved_v2`. Existing artifacts keep
|
||||
the original marker-free context, prompt, validation and feedback behavior.
|
||||
|
||||
The selected `entity_id` must still be present in `relevant_entities`. Its
|
||||
`source_ids` must include an original mention and either the entity alias or an
|
||||
inline `entity_name_lookup` fact backed by the **same capture** as that selected
|
||||
entity. A matching DB fact is sufficient identity evidence; a redundant N alias
|
||||
is not required. An unrelated fact cannot satisfy this requirement. Missing
|
||||
entities and missing provenance receive distinct error codes.
|
||||
|
||||
Correction feedback for the new prompt lists missing entities, the exact field,
|
||||
and permitted original-mention/capture aliases. It reports these even alongside
|
||||
source-kind errors, rather than waiting for multiple correction rounds to expose
|
||||
each issue. Tester observations and technical facts remain strictly separated.
|
||||
The prompt also distinguishes a scoped broad/localized lookup ambiguity from
|
||||
an independently selected, specifically named subject; the former does not by
|
||||
itself invalidate the latter.
|
||||
|
||||
The second real Gemini reply from the schema trial is an offline regression
|
||||
fixture. It is accepted with its original response and citations under the new
|
||||
policy; the old rule continues to reproduce the recorded historical rejection.
|
||||
This does not overwrite or accept artifacts in the exhausted REVIEW case.
|
||||
Reference in new issue
Block a user