model card draft
#1
by
ozyman
- opened
README.md
CHANGED
@@ -1,199 +1,109 @@
|
|
1 |
---
|
2 |
library_name: transformers
|
3 |
-
tags:
|
|
|
|
|
|
|
|
|
|
|
|
|
4 |
---
|
5 |
|
6 |
-
#
|
7 |
-
|
8 |
-
<!-- Provide a quick summary of what the model is/does. -->
|
9 |
-
|
10 |
-
|
11 |
|
12 |
## Model Details
|
13 |
|
14 |
### Model Description
|
15 |
|
16 |
-
|
17 |
|
18 |
-
|
19 |
-
|
20 |
-
- **
|
21 |
-
- **Funded by [optional]:** [More Information Needed]
|
22 |
-
- **Shared by [optional]:** [More Information Needed]
|
23 |
-
- **Model type:** [More Information Needed]
|
24 |
-
- **Language(s) (NLP):** [More Information Needed]
|
25 |
- **License:** [More Information Needed]
|
26 |
-
- **Finetuned from model
|
27 |
-
|
28 |
-
### Model Sources [optional]
|
29 |
-
|
30 |
-
<!-- Provide the basic links for the model. -->
|
31 |
-
|
32 |
-
- **Repository:** [More Information Needed]
|
33 |
-
- **Paper [optional]:** [More Information Needed]
|
34 |
-
- **Demo [optional]:** [More Information Needed]
|
35 |
|
36 |
## Uses
|
37 |
|
38 |
-
<!-- Address questions around how the model is intended to be used, including the foreseeable users of the model and those affected by the model. -->
|
39 |
-
|
40 |
### Direct Use
|
41 |
|
42 |
-
|
43 |
-
|
44 |
-
[More Information Needed]
|
45 |
-
|
46 |
-
### Downstream Use [optional]
|
47 |
|
48 |
-
|
49 |
|
50 |
-
|
51 |
|
52 |
### Out-of-Scope Use
|
53 |
|
54 |
-
|
55 |
-
|
56 |
-
[More Information Needed]
|
57 |
|
58 |
## Bias, Risks, and Limitations
|
59 |
|
60 |
-
|
61 |
-
|
62 |
-
[More Information Needed]
|
63 |
|
64 |
### Recommendations
|
65 |
|
66 |
-
|
67 |
-
|
68 |
-
Users (both direct and downstream) should be made aware of the risks, biases and limitations of the model. More information needed for further recommendations.
|
69 |
|
70 |
## How to Get Started with the Model
|
71 |
|
72 |
-
|
73 |
|
74 |
-
|
|
|
|
|
75 |
|
76 |
## Training Details
|
77 |
|
78 |
### Training Data
|
79 |
|
80 |
-
|
81 |
-
|
82 |
-
[More Information Needed]
|
83 |
|
84 |
### Training Procedure
|
85 |
|
86 |
-
<!-- This relates heavily to the Technical Specifications. Content here should link to that section when it is relevant to the training procedure. -->
|
87 |
-
|
88 |
#### Preprocessing [optional]
|
89 |
|
90 |
-
|
91 |
-
|
92 |
|
93 |
#### Training Hyperparameters
|
94 |
|
95 |
-
- **Training regime:** [More Information Needed]
|
96 |
-
|
97 |
-
#### Speeds, Sizes, Times [optional]
|
98 |
-
|
99 |
-
<!-- This section provides information about throughput, start/end time, checkpoint size if relevant, etc. -->
|
100 |
-
|
101 |
-
[More Information Needed]
|
102 |
|
103 |
## Evaluation
|
104 |
|
105 |
-
<!-- This section describes the evaluation protocols and provides the results. -->
|
106 |
-
|
107 |
### Testing Data, Factors & Metrics
|
108 |
|
109 |
#### Testing Data
|
110 |
|
111 |
-
|
112 |
-
|
113 |
-
[More Information Needed]
|
114 |
|
115 |
#### Factors
|
116 |
|
117 |
-
|
118 |
-
|
119 |
-
[More Information Needed]
|
120 |
|
121 |
#### Metrics
|
122 |
|
123 |
-
|
124 |
-
|
125 |
-
[More Information Needed]
|
126 |
|
127 |
### Results
|
128 |
|
129 |
-
|
130 |
-
|
131 |
-
#### Summary
|
132 |
-
|
133 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
134 |
|
135 |
-
|
136 |
-
|
137 |
-
<!-- Relevant interpretability work for the model goes here -->
|
138 |
-
|
139 |
-
[More Information Needed]
|
140 |
-
|
141 |
-
## Environmental Impact
|
142 |
-
|
143 |
-
<!-- Total emissions (in grams of CO2eq) and additional considerations, such as electricity usage, go here. Edit the suggested text below accordingly -->
|
144 |
-
|
145 |
-
Carbon emissions can be estimated using the [Machine Learning Impact calculator](https://mlco2.github.io/impact#compute) presented in [Lacoste et al. (2019)](https://arxiv.org/abs/1910.09700).
|
146 |
-
|
147 |
-
- **Hardware Type:** [More Information Needed]
|
148 |
-
- **Hours used:** [More Information Needed]
|
149 |
-
- **Cloud Provider:** [More Information Needed]
|
150 |
-
- **Compute Region:** [More Information Needed]
|
151 |
-
- **Carbon Emitted:** [More Information Needed]
|
152 |
-
|
153 |
-
## Technical Specifications [optional]
|
154 |
-
|
155 |
-
### Model Architecture and Objective
|
156 |
-
|
157 |
-
[More Information Needed]
|
158 |
-
|
159 |
-
### Compute Infrastructure
|
160 |
-
|
161 |
-
[More Information Needed]
|
162 |
-
|
163 |
-
#### Hardware
|
164 |
-
|
165 |
-
[More Information Needed]
|
166 |
-
|
167 |
-
#### Software
|
168 |
-
|
169 |
-
[More Information Needed]
|
170 |
-
|
171 |
-
## Citation [optional]
|
172 |
-
|
173 |
-
<!-- If there is a paper or blog post introducing the model, the APA and Bibtex information for that should go in this section. -->
|
174 |
-
|
175 |
-
**BibTeX:**
|
176 |
-
|
177 |
-
[More Information Needed]
|
178 |
-
|
179 |
-
**APA:**
|
180 |
-
|
181 |
-
[More Information Needed]
|
182 |
-
|
183 |
-
## Glossary [optional]
|
184 |
-
|
185 |
-
<!-- If relevant, include terms and calculations in this section that can help readers understand the model or model card. -->
|
186 |
-
|
187 |
-
[More Information Needed]
|
188 |
|
189 |
-
|
190 |
|
191 |
-
|
192 |
-
|
193 |
-
## Model Card Authors [optional]
|
194 |
|
195 |
[More Information Needed]
|
196 |
|
197 |
-
## Model Card Contact
|
198 |
-
|
199 |
-
[More Information Needed]
|
|
|
1 |
---
|
2 |
library_name: transformers
|
3 |
+
tags:
|
4 |
+
- verifcation
|
5 |
+
- policy_compliance
|
6 |
+
- factchecking
|
7 |
+
- instruction_following
|
8 |
+
base_model:
|
9 |
+
- akjindal53244/Llama-3.1-Storm-8B
|
10 |
---
|
11 |
|
12 |
+
# NAVI verifiers (Nace Automated Verification Intelligence)
|
|
|
|
|
|
|
|
|
13 |
|
14 |
## Model Details
|
15 |
|
16 |
### Model Description
|
17 |
|
18 |
+
NAVI (Nace Automated Verification Intelligence) is a solution for policy alignment verification designed to review various types of text against documents and policies, and identify violating content. It is specifically optimized for enterprise applications requiring compliance verification for automated text generation. To push policy verification in the open-source community, we release NAVI-small-preview, an open-weights version of the model we have deployed on the platform. NAVI-small-preview is centered around verifying specifically assitant outputs against some policy documents. The full solution is available on [NAVI platform](naviml.com).
|
19 |
|
20 |
+
- **Developed by:** Nace
|
21 |
+
- **Model type:** Policy Alignment Verifier
|
22 |
+
- **Language(s) (NLP):** English
|
|
|
|
|
|
|
|
|
23 |
- **License:** [More Information Needed]
|
24 |
+
- **Finetuned from model:** akjindal53244/Llama-3.1-Storm-8B
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
25 |
|
26 |
## Uses
|
27 |
|
|
|
|
|
28 |
### Direct Use
|
29 |
|
30 |
+
NAVI-small-preview is used for verifying compliance of assistant outputs with enterprise policy documents. It processes policies and identifies any contradictions, inconsistencies and violations.
|
|
|
|
|
|
|
|
|
31 |
|
32 |
+
### Downstream Use
|
33 |
|
34 |
+
May be integrated into enterprise-level AI systems to automate compliance checks in diverse industries such as legal, finance, and retail.
|
35 |
|
36 |
### Out-of-Scope Use
|
37 |
|
38 |
+
NAVI is not designed for general-purpose factuality verification or tasks unrelated to policy compliance.
|
|
|
|
|
39 |
|
40 |
## Bias, Risks, and Limitations
|
41 |
|
42 |
+
While NAVI excels in policy compliance verification, it may face challenges with unrealistic policy scenarios or contexts outside its training data scope.
|
|
|
|
|
43 |
|
44 |
### Recommendations
|
45 |
|
46 |
+
We recommend to use the model only as a generative classifier outputting the class label, any other outputs are not accounted for during training.
|
|
|
|
|
47 |
|
48 |
## How to Get Started with the Model
|
49 |
|
50 |
+
The verifier takes the assistant response and document context as inputs to generate a classification label. There are three possible classes: Compliant, Noncompliant, and Irrelevant. For long enterprise documents, we recommend setting up chunk-based vector search for selecting most relevant chunks from the document. Below are the prompts and sample code to launch:
|
51 |
|
52 |
+
```
|
53 |
+
|
54 |
+
```
|
55 |
|
56 |
## Training Details
|
57 |
|
58 |
### Training Data
|
59 |
|
60 |
+
NAVI was trained on a mix of real-world policy documents and synthetic interactions between a user and an assistant, it includes diverse, realistic, and complex policy examples across multiple industries.
|
|
|
|
|
61 |
|
62 |
### Training Procedure
|
63 |
|
|
|
|
|
64 |
#### Preprocessing [optional]
|
65 |
|
66 |
+
Policies are processed into embeddings for effective decision-making.
|
|
|
67 |
|
68 |
#### Training Hyperparameters
|
69 |
|
70 |
+
- **Training regime:** [More Information Needed]
|
|
|
|
|
|
|
|
|
|
|
|
|
71 |
|
72 |
## Evaluation
|
73 |
|
|
|
|
|
74 |
### Testing Data, Factors & Metrics
|
75 |
|
76 |
#### Testing Data
|
77 |
|
78 |
+
We have manually collected Policy Alignment Verification dataset consisting of across different use cases for evaluation. We open source the public subset of the dataset. Here we diclose the performance on the public subset, containing 125 examples across six industry-specific scenarios: AT&T, Airbnb, Cadence Bank, Delta Airlines, Verisk, and Walgreens.
|
|
|
|
|
79 |
|
80 |
#### Factors
|
81 |
|
82 |
+
Evaluation focuses on policy compliance within multi-policy, multi-document contexts.
|
|
|
|
|
83 |
|
84 |
#### Metrics
|
85 |
|
86 |
+
F1 score was used to measure performance, prioritizing detection of noncompliance cases.
|
|
|
|
|
87 |
|
88 |
### Results
|
89 |
|
90 |
+
NAVI-small-preview achieved an F1 score of 86.8%, outperforming all evaluated alternatives except full-scale NAVI. We evaluate against general-purpose solutions like Claude and Open AI models, as well as some guardrails focusing on factchecking to demonstrate a clear distinction of policy verification from the more common factchecking. Full performance metrics:
|
|
|
|
|
|
|
91 |
|
92 |
+
| Model | F1 Score | Avg Latency (ms) |
|
93 |
+
|--------------------------|----------|------------------|
|
94 |
+
| NAVI-small-preview | 86.8 | - |
|
95 |
+
| NAVI | 90.4 | 387.62 |
|
96 |
+
| AWS Bedrock Guardrail | 76.5 | 342.79 |
|
97 |
+
| Azure Groundedness | 71.2 | 232.71 |
|
98 |
+
| NeMo (GPT-4o) | 71.2 | 2669.68 |
|
99 |
+
| GPT-4o (few-shot) | 75.0 | 904.46 |
|
100 |
+
| Sonnet 3.5 (few-shot) | 75.5 | 2926.69 | ()
|
101 |
|
102 |
+
#### Summary
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
103 |
|
104 |
+
NAVI demonstrates clear advantages in both performance and efficiency, making it a robust solution for policy compliance verification.
|
105 |
|
106 |
+
## Model Card Contact
|
|
|
|
|
107 |
|
108 |
[More Information Needed]
|
109 |
|
|
|
|
|
|