arvind6599 commited on
Commit
6de33d2
·
1 Parent(s): 053ea77

Fixed formatting errors:

Browse files
Files changed (1) hide show
  1. app.py +17 -19
app.py CHANGED
@@ -334,30 +334,28 @@ def build_interface():
334
  """
335
  with gr.Blocks() as demo:
336
  gr.Markdown("""
337
- # Applicant Task: Target Company & Law Firm Identification
338
 
339
- ---
340
 
341
- This task involves processing a user query to determine the relevance to the intended task, followed by analyzing textual data to extract information about law firms representing parties (Buyer, Seller, and Third Parties) and verifying the presence of a target company. You can refer to the following legal document: [SEC Agreement Example](https://www.sec.gov/Archives/edgar/data/28452/000119312505012401/dex101.html)
342
 
343
- The system is designed to sequentially leverage three LLM functions:
 
 
 
344
 
345
- ### Step 1: LLM1
346
- - Determines if the user's query mentions any target company.
347
- - If no target company is found, LLM1 responds with a message wrapped in `<user_message></user_message>` XML tags to inform the user that the query is irrelevant to this task.
348
- - If the query contains a target company, LLM1 moves forward with a formatted acknowledgment of the identified target company.
 
 
 
 
349
 
350
- ### Step 2: LLM2
351
- - Examines four separate paragraphs independently.
352
- - For each paragraph, extracts:
353
- - Buyer's representative law firm
354
- - Seller's representative law firm
355
- - Any third-party law firm present
356
- - Whether the target company is mentioned in the paragraph
357
- - Each paragraph's results are formatted and concatenated for the next step.
358
-
359
- ### Step 3: LLM3
360
- - Compiles the information from all analyzed paragraphs and outputs a structured JSON object:
361
 
362
  ```json
363
  {
 
334
  """
335
  with gr.Blocks() as demo:
336
  gr.Markdown("""
337
+ # Applicant Task: Target Company & Law Firm Identification
338
 
339
+ This task involves processing a user query to determine the relevance to the intended task, followed by analyzing textual data to extract information about law firms representing parties (Buyer, Seller, and Third Parties) and verifying the presence of a target company. You can refer to the following legal document: [SEC Agreement Example](https://www.sec.gov/Archives/edgar/data/28452/000119312505012401/dex101.htm)
340
 
341
+ The system is designed to sequentially leverage three LLM functions:
342
 
343
+ ### Step 1: LLM1
344
+ - Determines if the user's query mentions any target company.
345
+ - If no target company is found, LLM1 responds with a message wrapped in `<user_message></user_message>` XML tags to inform the user that the query is irrelevant to this task.
346
+ - If the query contains a target company, LLM1 moves forward with a formatted acknowledgment of the identified target company.
347
 
348
+ ### Step 2: LLM2
349
+ - Examines four separate paragraphs independently.
350
+ - For each paragraph, extracts:
351
+ - Buyer's representative law firm
352
+ - Seller's representative law firm
353
+ - Any third-party law firm present
354
+ - Whether the target company is mentioned in the paragraph
355
+ - Each paragraph's results are formatted and concatenated for the next step.
356
 
357
+ ### Step 3: LLM3
358
+ - Compiles the information from all analyzed paragraphs and outputs a structured JSON object:
 
 
 
 
 
 
 
 
 
359
 
360
  ```json
361
  {