Update README.md
Browse files
README.md
CHANGED
@@ -1,199 +1,90 @@
|
|
1 |
---
|
2 |
-
|
3 |
-
|
|
|
|
|
|
|
|
|
|
|
4 |
---
|
5 |
|
6 |
-
#
|
7 |
-
|
8 |
-
|
9 |
-
|
10 |
-
|
11 |
-
|
12 |
-
|
13 |
-
|
14 |
-
|
15 |
-
|
16 |
-
|
17 |
-
|
18 |
-
|
19 |
-
|
20 |
-
- **
|
21 |
-
- **
|
22 |
-
- **
|
23 |
-
- **
|
24 |
-
- **
|
25 |
-
- **
|
26 |
-
- **
|
27 |
-
|
28 |
-
|
29 |
-
|
30 |
-
|
31 |
-
|
32 |
-
|
33 |
-
|
34 |
-
- **
|
35 |
-
|
36 |
-
|
37 |
-
|
38 |
-
|
39 |
-
|
40 |
-
|
41 |
-
|
42 |
-
|
43 |
-
|
44 |
-
|
45 |
-
|
46 |
-
|
47 |
-
|
48 |
-
|
49 |
-
|
50 |
-
|
51 |
-
|
52 |
-
|
53 |
-
|
54 |
-
|
55 |
-
|
56 |
-
|
57 |
-
|
58 |
-
|
59 |
-
|
60 |
-
|
61 |
-
|
62 |
-
|
63 |
-
|
64 |
-
|
65 |
-
|
66 |
-
|
67 |
-
|
68 |
-
|
69 |
-
|
70 |
-
|
71 |
-
|
72 |
-
|
73 |
-
|
74 |
-
|
75 |
-
|
76 |
-
|
77 |
-
|
78 |
-
|
79 |
-
|
80 |
-
|
81 |
-
|
82 |
-
|
83 |
-
|
84 |
-
|
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 |
-
#### 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 |
-
## More Information [optional]
|
190 |
-
|
191 |
-
[More Information Needed]
|
192 |
-
|
193 |
-
## Model Card Authors [optional]
|
194 |
-
|
195 |
-
[More Information Needed]
|
196 |
-
|
197 |
-
## Model Card Contact
|
198 |
-
|
199 |
-
[More Information Needed]
|
|
|
1 |
---
|
2 |
+
language:
|
3 |
+
- en
|
4 |
+
metrics:
|
5 |
+
- accuracy
|
6 |
+
- f1
|
7 |
+
- precision
|
8 |
+
- recall
|
9 |
---
|
10 |
|
11 |
+
# Phi-3-medium-4k-instruct for Stance Detection
|
12 |
+
|
13 |
+
## Model Description
|
14 |
+
|
15 |
+
This model is a fine-tuned version of ´unsloth/Phi-3-medium-4k-instruct´ for stance detection on online discussions.
|
16 |
+
Within an argument map, i.e. a tree structure representing a debate, the model can be used to identify the stance of a claim toward its parent claim. This model is part of SAGESSE, a pipeline for processing data from Reddit threads to create argument maps. In the context of SAGESSE pipeline, the claims that are processed by this stance detection model are extracted using the [SAGESSE-EPFL/Mistral-7b-claims-extraction](https://huggingface.co/SAGESSE-EPFL/Mistral-7b-claims-extraction) model on Reddit comments.
|
17 |
+
|
18 |
+
|
19 |
+
## Training and Fine-Tuning
|
20 |
+
- **Base Model**: [´unsloth/Phi-3-medium-4k-instruct´](https://huggingface.co/unsloth/Phi-3-medium-4k-instruct)
|
21 |
+
- **Fine-Tuning Data**:
|
22 |
+
- **Claims Extraction Dataset**: ~50k claim pairs with relative stance from [Kialo](https://www.kialo.com)
|
23 |
+
- **Annotation Source**: dataset extracted from the debate platform [Kialo](https://www.kialo.com).
|
24 |
+
- **Fine-Tuning Approach**:
|
25 |
+
- **Technique**: Parameter Efficient Fine-Tuning (PEFT) using Low-Rank Adaptation (LoRA).
|
26 |
+
- **Training Configuration**:
|
27 |
+
- **Epochs**: 2
|
28 |
+
- **Learning Rate**: 2e-4
|
29 |
+
- **Batch Size**: 2
|
30 |
+
- **Gradient Accumulation Steps**: 16
|
31 |
+
- **Hardware**: Single Nvidia A100 GPU with 40GB memory
|
32 |
+
- **LoRA Rank**: 16
|
33 |
+
- **LoRA Alpha**: 16
|
34 |
+
- **Libraries Used**: HuggingFace’s Transformers library
|
35 |
+
|
36 |
+
|
37 |
+
|
38 |
+
## Performance
|
39 |
+
- **Evaluation Metric**: weighted F1 score over the three classes _Positive_, _Negative_ and _Neutral_
|
40 |
+
- **Evaluation Datasets**:
|
41 |
+
- - Kialo test set
|
42 |
+
- stances extracted from ChangeMyView v2.0 (used to assess generalization to different domain)
|
43 |
+
- **Performance**:
|
44 |
+
Note that the performance have been tested both using directly the fine-tuned model with zero-shots prompting, and the fine-tuned model with 3 relevant shots (chosen by cosine similarity).
|
45 |
+
- Kialo test set:
|
46 |
+
- Fine-Tuned model with zero-shots:
|
47 |
+
- **F1 Score**: 0.874
|
48 |
+
- Fine-Tuned model with 3-shots:
|
49 |
+
- **F1 Score**: 0.855
|
50 |
+
- ChangeMyView:
|
51 |
+
- Fine-Tuned model with zero-shots:
|
52 |
+
- **F1 Score**: 0.755
|
53 |
+
- Fine-Tuned model with 3-shots:
|
54 |
+
- **F1 Score**: 0.740
|
55 |
+
|
56 |
+
|
57 |
+
|
58 |
+
## Usage
|
59 |
+
This model is intended for use in systems that require stance detection from text, particularly in contexts like argument mapping, content moderation, or sentiment analysis.
|
60 |
+
|
61 |
+
### Input Format
|
62 |
+
The model was used with the following prompt template:
|
63 |
+
```txt
|
64 |
+
Below is an instruction that describes a task, paired with an input that provides further context.
|
65 |
+
Write a response that appropriately completes the request.
|
66 |
+
|
67 |
+
### Instruction:
|
68 |
+
You are tasked with stance detection in a debate context. The provided discussions come from a variety of political subreddits on Reddit.
|
69 |
+
Each discussion includes a parent opinion and various claims that support, oppose, or are neutral to it. Your job is to determine the stance
|
70 |
+
of the given claim with respect to the parent opinion. Make sure to carefully consider the context and the content of both the parent opinion
|
71 |
+
and the claim to determine the correct stance. You have three options to choose from for determining the stance: Positive, Negative, and Neutral.
|
72 |
+
|
73 |
+
### Input:
|
74 |
+
Parent Opinion: <parent-claim>
|
75 |
+
Claim: <claim>
|
76 |
+
|
77 |
+
### Response:
|
78 |
+
```
|
79 |
+
|
80 |
+
### Output
|
81 |
+
The model is used to generate one single token, improving throughput at inference time.
|
82 |
+
|
83 |
+
## Citation
|
84 |
+
If you use this model in your research, please cite the following paper:
|
85 |
+
```bibtex
|
86 |
+
TBD
|
87 |
+
```
|
88 |
+
|
89 |
+
## Contact Information
|
90 |
+
For questions or issues, please contact [Matteo Santelmo](https://github.com/matteosantelmo) at matteo.santelmo@epfl.ch.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|