Lynx Pilot 1. Research Meets Practice (ReMeP 2019)

1. Building the Legal Knowledge Graph
for Smart Compliance Services in Multilingual Europe
http://lynx-project.eu/
Lynx
Pilot 1
Christian Sageder
Salzburg, 1st October 2019

2. ENVISIONED SOLUTION
annotation
linking
classification
Trust /
Security
Legal
resources
Language
resources
Standards
Private
documents
Other
open data
Linked Data
Vocabulary
Indexed
Documents
Legal Knowledge Graph
translation
Workflows
Smart
Services
Pilot
Contracts
Pilot
Geo-Thermal
Pilot
Labor Law
linking
recommend
semantic
annotation
summa-
rization
extraction
search
ETL
API
Q&A
…

3. PILOT CONTRACTS
Contract processing is costful in terms of time and money.
• How to process contracts in a fast and efficient manner?
• Which clauses are senstive regarding changes in the
legislation?
• Are there decisions which have
impacts to my contracts?
• How to get an overview of
contracts in other languages?

4. ENVISIONED USE CASE
Input: Files in multiple
input formats: e.g.
mail, word, pdf
Local
KG
Lynx Services
Summ
(Trans)
TimEx
Output:
Extracted / Calculated
Data Information Extraction:
type, parties,
places, addresses, time and
dates, deadlines, applicable
law, contract clause
T&C references, ...
Classification
Contracts, orders,
notice, emails, …
Openlaws backend
NER
Text Extraction
Building a Document
Structure
Knowledge Extraction
Generating Output
Custom implementation
EntEx
Geo
(SeSim)

5. WHAT WE HAVE
• Services to make a nif file out of
• PDF (incl OCR)
• MS-OFFICE
• IMAGES, e.g tiff, jpeg (incl OCR)
• e-Mails (Outlook msg, rfc822)
• Service to combine a annotated nif and a pdf to create put
annotations inside the pdf
• Service to annotate documents based on reg-ex rfc822

6. WHAT IS MISSING
• Use of the annotation workflow, to get the annotations from the
different lynx services
• GUI for the demo
• Concept currently WIP, should be finished by mid of October
• Grafical design,

7. CONTRACT ANALYSIS
7

8. EXAMPLE SCORING
To calculate the increasing cost for a contract the
following information is needed:
• Which Index is agreed (this example:
VPI 2010)
• Which Interval (this example: yearly)
• What is the starting point for the calculation (this
example: der Monat, in dem das Angebot gelegt
wurde and 28.05.2019)
• Is there a threshold value (this example: no)
• The relevant Amount
• The relevant data of the customer
In addition data from external systems are used:
• ERP System of the client
• Statistik Austria – Index value
Indexsicherung: Die Preise unterliegen einer jährlichen
Wertsicherung nach dem Verbraucherpreisindex (VPI) 2010
oder dem an seine Stelle tretenden Index. Ausgangsbasis
für die Wertsicherungsberechnung ist die für den Monat, in
dem das gegenständliche Angebot gelegt wurde,
verlautbarte Indexzahl.
Einmalige Kosten € 677,30
Monatliche Kosten € 131,81
28.05.2019

9. DEMO
• http://order-extractor-88-
contracts.cloud.itandtel.at/api/view/index.html

10. CONTRIBUTION
• Further Pilots
• We are looking for further companies which also want to make a pilot to
prof the functionality of Lynx
• On one's own account
• We are hiring

11. CONTACTS
CONSORTIUM
Elena Montiel-Ponsoda
Lynx Coordinator
Ontology Engineering Group, UPM
+34-91-336-3670/7414
emontiel@fi.upm.es