Update README.md
Browse files
README.md
CHANGED
@@ -1,199 +1,102 @@
|
|
1 |
---
|
2 |
library_name: transformers
|
3 |
-
tags:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4 |
---
|
5 |
|
6 |
-
# Model Card
|
7 |
-
|
8 |
-
<!-- Provide a quick summary of what the model is/does. -->
|
9 |
|
|
|
10 |
|
|
|
11 |
|
12 |
## Model Details
|
13 |
|
14 |
-
|
15 |
-
|
16 |
-
|
17 |
-
|
18 |
-
|
19 |
-
|
20 |
-
- **Developed by:** [More Information Needed]
|
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 [optional]:** [More Information Needed]
|
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 |
-
<!-- This section is for the model use without fine-tuning or plugging into a larger ecosystem/app. -->
|
43 |
-
|
44 |
-
[More Information Needed]
|
45 |
-
|
46 |
-
### Downstream Use [optional]
|
47 |
-
|
48 |
-
<!-- This section is for the model use when fine-tuned for a task, or when plugged into a larger ecosystem/app -->
|
49 |
-
|
50 |
-
[More Information Needed]
|
51 |
-
|
52 |
-
### Out-of-Scope Use
|
53 |
-
|
54 |
-
<!-- This section addresses misuse, malicious use, and uses that the model will not work well for. -->
|
55 |
-
|
56 |
-
[More Information Needed]
|
57 |
-
|
58 |
-
## Bias, Risks, and Limitations
|
59 |
-
|
60 |
-
<!-- This section is meant to convey both technical and sociotechnical limitations. -->
|
61 |
-
|
62 |
-
[More Information Needed]
|
63 |
-
|
64 |
-
### Recommendations
|
65 |
-
|
66 |
-
<!-- This section is meant to convey recommendations with respect to the bias, risk, and technical limitations. -->
|
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 |
-
Use the code below to get started with the model.
|
73 |
-
|
74 |
-
[More Information Needed]
|
75 |
-
|
76 |
-
## Training Details
|
77 |
-
|
78 |
-
### Training Data
|
79 |
-
|
80 |
-
<!-- This should link to a Dataset Card, perhaps with a short stub of information on what the training data is all about as well as documentation related to data pre-processing or additional filtering. -->
|
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 |
-
[More Information Needed]
|
91 |
-
|
92 |
-
|
93 |
-
#### Training Hyperparameters
|
94 |
-
|
95 |
-
- **Training regime:** [More Information Needed] <!--fp32, fp16 mixed precision, bf16 mixed precision, bf16 non-mixed precision, fp16 non-mixed precision, fp8 mixed precision -->
|
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 |
-
<!-- This should link to a Dataset Card if possible. -->
|
112 |
-
|
113 |
-
[More Information Needed]
|
114 |
-
|
115 |
-
#### Factors
|
116 |
-
|
117 |
-
<!-- These are the things the evaluation is disaggregating by, e.g., subpopulations or domains. -->
|
118 |
-
|
119 |
-
[More Information Needed]
|
120 |
-
|
121 |
-
#### Metrics
|
122 |
-
|
123 |
-
<!-- These are the evaluation metrics being used, ideally with a description of why. -->
|
124 |
-
|
125 |
-
[More Information Needed]
|
126 |
-
|
127 |
-
### Results
|
128 |
-
|
129 |
-
[More Information Needed]
|
130 |
-
|
131 |
-
#### Summary
|
132 |
-
|
133 |
-
|
134 |
-
|
135 |
-
## Model Examination [optional]
|
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 |
-
|
164 |
|
165 |
-
|
|
|
|
|
|
|
166 |
|
167 |
-
|
|
|
|
|
|
|
168 |
|
169 |
-
|
170 |
|
171 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
172 |
|
173 |
-
|
174 |
|
175 |
-
**
|
|
|
|
|
176 |
|
177 |
-
|
178 |
|
179 |
-
|
180 |
|
181 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
182 |
|
183 |
-
|
|
|
|
|
|
|
184 |
|
185 |
-
|
186 |
|
187 |
-
|
|
|
|
|
|
|
188 |
|
189 |
-
|
190 |
|
191 |
-
|
192 |
|
193 |
-
|
|
|
194 |
|
195 |
-
|
196 |
|
197 |
-
|
198 |
|
199 |
-
|
|
|
|
|
|
1 |
---
|
2 |
library_name: transformers
|
3 |
+
tags:
|
4 |
+
- Website Classification
|
5 |
+
license: mit
|
6 |
+
datasets:
|
7 |
+
- Shahriar/websector-corpus
|
8 |
+
language:
|
9 |
+
- en
|
10 |
+
base_model: FacebookAI/roberta-base
|
11 |
+
pipeline_tag: text-classification
|
12 |
---
|
13 |
|
14 |
+
# WebSector-Flexible Model Card
|
|
|
|
|
15 |
|
16 |
+
## Model Overview
|
17 |
|
18 |
+
The WebSector-Flexible model is a transformer-based multi-sector website classification model, fine-tuned using the RoBERTa architecture with LoRA and trained on the WebSector dataset, consisting of 109,476 websites in the training set. The flexible mode is designed to maximize recall by identifying both primary and secondary sectors of websites, making it suitable for applications that require broad coverage across multiple sectors. This mode is ideal for exploratory tasks or when it's critical to capture all possible sector associations.
|
19 |
|
20 |
## Model Details
|
21 |
|
22 |
+
- **Model type**: Transformer-based (RoBERTa + LoRA)
|
23 |
+
- **Training dataset**: WebSector Corpus (Training set: 109,476 websites)
|
24 |
+
- **Prediction modes**: Flexible mode
|
25 |
+
- **Task**: Multi-sector website classification
|
26 |
+
- **Architecture**: RoBERTa transformer fine-tuned with LexRank summarization for handling lengthy content
|
27 |
+
- **Special Technique**: Single Positive Label (SPL) paradigm for multi-label classification with WAN loss
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
28 |
|
29 |
+
## Intended Uses & Limitations
|
30 |
|
31 |
+
### Use Cases
|
32 |
+
- **Website categorization**: Classifies websites into multiple sectors for general exploration or broader categorization tasks.
|
33 |
+
- **Research**: Suitable for research on multi-sector classification or multi-label classification tasks where label dependencies are important.
|
34 |
+
- **Content Management**: Can be used in platforms where it's important to categorize content across multiple industries or sectors.
|
35 |
|
36 |
+
### Limitations
|
37 |
+
- **Single Positive Label**: Trained with only the primary sector observable, potentially limiting its accuracy in predicting secondary sectors.
|
38 |
+
- **Flexible mode**: Focuses on recall, which may lead to over-predicting some sectors in websites with ambiguous content.
|
39 |
+
- **Data Imbalance**: Some sectors are underrepresented in the dataset, which may affect model performance on certain sectors.
|
40 |
|
41 |
+
## Dataset
|
42 |
|
43 |
+
- **Dataset name**: WebSector Corpus
|
44 |
+
- **Training set size**: 109,476 websites
|
45 |
+
- **Sectors**:
|
46 |
+
1. Finance, Marketing & HR
|
47 |
+
2. Information Technology & Electronics
|
48 |
+
3. Consumer & Supply Chain
|
49 |
+
4. Civil, Mechanical & Electrical
|
50 |
+
5. Medical
|
51 |
+
6. Sports, Media & Entertainment
|
52 |
+
7. Education
|
53 |
+
8. Government, Defense & Legal
|
54 |
+
9. Travel, Food & Hospitality
|
55 |
+
10. Non-Profit
|
56 |
+
- **Labeling**: Each website is labeled with its primary sector, derived from self-declared industry categories.
|
57 |
|
58 |
+
## Evaluation Metrics
|
59 |
|
60 |
+
- **Top-1 Recall**: Measures the model's ability to correctly identify the primary sector as the most likely predicted sector.
|
61 |
+
- **Top-3 Recall**: Evaluates the model's capacity to have the true sector within the top three predicted labels.
|
62 |
+
- **Recall**: Assesses the model's ability to predict all relevant sectors, not just the primary one.
|
63 |
|
64 |
+
The flexible mode maximizes recall, making it ideal for capturing as many relevant sectors as possible, though it may compromise precision.
|
65 |
|
66 |
+
## Training Process
|
67 |
|
68 |
+
### Hyperparameters:
|
69 |
+
- Number of epochs: 7
|
70 |
+
- Batch size: 8
|
71 |
+
- Learning rate: 5×10^-6
|
72 |
+
- Weight decay: 0.1
|
73 |
+
- LoRA rank: 128
|
74 |
+
- LoRA alpha: 512
|
75 |
+
- Dropout rate: 0.1
|
76 |
|
77 |
+
### Training Setup:
|
78 |
+
- **Hardware**: Four GPUs, including two NVIDIA RTX A5000 and two NVIDIA TITAN RTX units for parallel processing.
|
79 |
+
- **Software**: PyTorch framework and Hugging Face Transformers library.
|
80 |
+
- **Strategy**: Distributed training across four GPUs, with model selection based on the lowest validation loss.
|
81 |
|
82 |
+
## Model Performance
|
83 |
|
84 |
+
- Top-1 Recall: 68%
|
85 |
+
- Top-3 Recall: 85%
|
86 |
+
- Recall: 86%
|
87 |
+
- Precision: 68%
|
88 |
|
89 |
+
These metrics show that the flexible mode of the WebSector model is optimized for recall, allowing it to capture multiple relevant sectors while maintaining a solid precision score.
|
90 |
|
91 |
+
## Ethical Considerations
|
92 |
|
93 |
+
- **Privacy Enforcement**: This model can assist in classifying websites into sectors relevant to privacy regulations like CCPA or HIPAA.
|
94 |
+
- **Bias**: As the model was trained on self-declared sector labels, there is potential for bias due to inaccurate or incomplete labeling.
|
95 |
|
96 |
+
## Citation
|
97 |
|
98 |
+
If you use this model in your research, please cite the following paper:
|
99 |
|
100 |
+
```
|
101 |
+
Shahriar Shayesteh, Mukund Srinath, Lee Matheson, Florian Schaub, C. Lee Giles, and Shomir Wilson. "WebSector: A New Insight into Multi-Sector Website Classification Using Single Positive Labels". Conference acronym 'XX, June 03–05, 2018, Woodstock, NY.
|
102 |
+
```
|