Merged in bugfix/json_and_unit_of_measure (pull request #709)

json parsing fix

* OUTLIER_TERMS-->OUTLIER_TERM standardization

* Applied suggestion to fieldExtraction/src/prompts/investment_prompts.json
* update unit test

* Update Carveout IND and Default IND logic

* Split out exhibit-level lesser

* Bugfix

* update lesser of exhibit prompt

* Bugfix

* exhibit lesser of varible name bugfix

* Update exhibit lesser of passing

* Update Exhibit-level prompt template

* Shorten full_context prompt length if the questions are long

* Special case assignment index

* Resolve unit tests

* updated UC IND prompt

* Remove print

* update one-to-n unit test

* added dot based date example

* updated date fix prompt

* Merged in bugfix/json_error_and_unit_of_measure (pull request #708)

Bugfix/json error and unit of measure

* json parser fixes and prompt changes

* universal json load fixed

* json error fixed

* json error fixed 2

* Merged refactor/one-to-n into bugfix/json_error_and_unit_of_measure


Approved-by: Katon Minhas

* json parsing fix

* prompt update

* Merge branch 'main' into bugfix/json_and_unit_of_measure

* minor bugfix

* minor bugfix


Approved-by: Alex Galarce
This commit is contained in:
Mayank Aamseek
2025-09-25 14:16:56 +00:00
committed by Alex Galarce
parent f12d753b92
commit 4651248ca3
2 changed files with 4 additions and 2 deletions
File diff suppressed because one or more lines are too long
@@ -740,13 +740,15 @@ def ONE_TO_ONE_MULTI_FIELD_TEMPLATE(context, questions: dict[str, str]):
{context.replace('"', "'")}
## END CONTRACT TEXT ##
For each question, explain your reasoning. Then provide your final answers in a JSON dictionary format.
For each question, explain your reasoning. Then provide your final answers in a JSON dictionary format. Explanation MUST NOT contain any curly brackets '{{' or '}}'. Replace them with '()' instead.
The JSON should:
- Include every key
- Use 'N/A' for any question where the requested information doesn't apply to this context
- Use 'UNKNOWN' for any question where the requested information should exist but cannot be clearly identified
- Contain only the final answers, not explanations
- NOT contain any curly brackets '{{' or '}}' inside.
- If curly bracket still exists inside JSON, replace them with '()' instead.
Example format:
I found the effective date in section 2.1 which states...