Model: rchrdgwr/finetuned-arctic-model-2
Author: rchrdgwr
Pipeline: sentence-similarity
Library: sentence-transformers
Tags: sentence-transformers, safetensors, bert, sentence-similarity, feature-extraction, generated_from_trainer, dataset_size:568, loss:MatryoshkaLoss, loss:MultipleNegativesRankingLoss, arxiv:1908.10084, arxiv:2205.13147, arxiv:1705.00652, base_model:Snowflake/snowflake-arctic-embed-m, base_model:finetune:Snowflake/snowflake-arctic-embed-m, model-index, text-embeddings-inference, endpoints_compatible, region:us
Base models (finetune): id: Snowflake/snowflake-arctic-embed-m
Card metadata: base_model: Snowflake/snowflake-arctic-embed-m
library_name: sentence-transformers
metrics: cosine_accuracy@1, cosine_accuracy@3, cosine_accuracy@5, cosine_accuracy@10, cosine_precision@1, cosine_precision@3, cosine_precision@5, cosine_precision@10, cosine_recall@1, cosine_recall@3, cosine_recall@5, cosine_recall@10, cosine_ndcg@10, cosine_mrr@10, cosine_map@100, dot_accuracy@1, dot_accuracy@3, dot_accuracy@5, dot_accuracy@10, dot_precision@1, dot_precision@3, dot_precision@5, dot_precision@10, dot_recall@1, dot_recall@3, dot_recall@5, dot_recall@10, dot_ndcg@10, dot_mrr@10, dot_map@100
pipeline_tag: sentence-similarity
tags: sentence-transformers, sentence-similarity, feature-extraction, generated_from_trainer, dataset_size:568, loss:MatryoshkaLoss, loss:MultipleNegativesRankingLoss
widget: source_sentence: What measures did the device manufacturer take to protect individuals from unwanted tracking?
sentences: Tailored to the target of the explanation. Explanations should be targeted to specific audiences and clearly state that audience. An explanation provided to the subject of a decision might differ from one provided to an advocate, or to a domain expert or decision maker. Tailoring should be assessed (e.g., via user experience research). 
43
      NOTICE & 
EXPLANATION 
WHAT SHOULD BE EXPECTED OF AUTOMATED SYSTEMS
The expectations for automated systems are meant to serve as a blueprint for the development of additional 
technical standards and practices that are tailored for particular sectors and contexts. 
Tailored to the level of risk. An assessment should be done to determine the level of risk of the auto -, 7
• A device originally developed to help people track and find lost items has been used as a tool by stalkers to trackvictims’ locations in violation of their privacy and safet y. The device manufacturer took steps after release to
protect people from unwanted tracking by alerting people on their phones when a device is found to be movingwith them over time and also by having the device make an occasional noise, but not all phones are ableto receive the notification and the devices remain a safety concern due to their misuse.
8, -
sonable expectations in a given context and with a focus on ensuring broad accessibility and protecting the public from especially harm
-
ful impacts. In some cases, a human or other alternative may be re -
quired by law. You should have access to timely human consider -
ation and remedy by a fallback and escalation process if an automat -
ed system fails, it produces an error, or you would like to appeal or contest its impacts on you. Human consideration and fallback should be accessible, equitable, effective, maintained, accompanied by appropriate operator training, and should not impose an unrea
-, source_sentence: Why is ongoing monitoring and mitigation important for automated systems after deployment?
sentences: -
test its impacts on you 
Proportionate. The availability of human consideration and fallback, along with associated training and 
safeguards against human bias, should be proportionate to the potential of the automated system to meaning -
fully impact rights, opportunities, or access. Automated systems that have greater control over outcomes, provide input to high-stakes decisions, relate to sensitive domains, or otherwise have a greater potential to meaningfully impact rights, opportunities, or access should have greater availability (e.g., staffing) and over
-
sight of human consideration and fallback mechanisms. 
Accessible. Mechanisms for human consideration and fallback, whether in-person, on paper, by phone, or, algorithmic discrimination, avoid meaningful harm, and achieve equity goals. 
Ongoing monitoring and mitigation. Automated systems should be regularly monitored to assess algo -
rithmic discrimination that might arise from unforeseen interactions of the system with inequities not accounted for during the pre-deployment testing, changes to the system after deployment, or changes to the context of use or associated data. Monitoring and disparity assessment should be performed by the entity deploying or using the automated system to examine whether the system has led to algorithmic discrimina
-, The expectations for automated systems are meant to serve as a blueprint for the development of additional 
technical standards and practices that are tailored for particular sectors and contexts. 
Ongoing monitoring. Automated systems should have ongoing monitoring procedures, including recalibra -
tion procedures, in place to ensure that their performance does not fall below an acceptable level over time, 
based on changing real-world conditions or deployment contexts, post-deployment modification, or unexpect -, source_sentence: What should be included in the measurement of the impact of risks associated with automated systems?
sentences: 104 
48
      HUMAN ALTERNATIVES, 
CONSIDERATION, AND 
FALLBACK 
WHAT SHOULD BE EXPECTED OF AUTOMATED SYSTEMS
The expectations for automated systems are meant to serve as a blueprint for the development of additional 
technical standards and practices that are tailored for particular sectors and contexts. 
An automated system should provide demonstrably effective mechanisms to opt out in favor of a human alterna -
tive, where appropriate, as well as timely human consideration and remedy by a fallback system, with additional 
human oversight and safeguards for systems used in sensitive domains, and with training and assessment for any human-based portions of the system to ensure effectiveness., collection and use is legal and consistent with the expectations of the people whose data is collected. User experience research should be conducted to confirm that people understand what data is being collected about them and how it will be used, and that this collection matches their expectations and desires., -
surement of the impact of risks should be included and balanced such that high impact risks receive attention and mitigation proportionate with those impacts. Automated systems with the intended purpose of violating the safety of others should not be developed or used; systems with such safety violations as identified unin
-
tended consequences should not be used until the risk can be mitigated. Ongoing risk mitigation may necessi -
tate rollback or significant modification to a launched automated system. 
18
      
 
 
 
 
  SAFE AND EFFECTIVE 
SYSTEMS 
WHAT SHOULD BE EXPECTED OF AUTOMATED SYSTEMS
The expectations for automated systems are meant to serve as a blueprint for the development of additional, source_sentence: What measures should be taken to avoid "mission creep" when identifying goals for data collection?
sentences: narrow identified goals, to avoid "mission creep."  Anticipated data collection should be determined to be strictly necessary to the identified goals and should be minimized as much as possible. Data collected based on these identified goals and for a specific context should not be used in a different context without assessing for new privacy risks and implementing appropriate mitigation measures, which may include express consent. Clear timelines for data retention should be established, with data deleted as soon as possible in accordance with legal or policy-based limitations. Determined data retention timelines should be documented and justi
-
fied., with more and more companies tracking the behavior of the American public, building individual profiles based on this data, and using this granular-level information as input into automated systems that further track, profile, and impact the American public. Government agencies, particularly law enforcement agencies, also use and help develop a variety of technologies that enhance and expand surveillance capabilities, which similarly collect data used as input into other automated systems that directly impact people’s lives. Federal law has not grown to address the expanding scale of private data collection, or of the ability of governments at all levels to access that data and leverage the means of private collection., additional technical standards and practices that should be tailored for particular sectors and contexts. While 
existing laws informed the development of the Blueprint for an AI Bill of Rights, this framework does not detail those laws beyond providing them as examples, where appropriate, of existing protective measures. This framework instead shares a broad, forward-leaning vision of recommended principles for automated system development and use to inform private and public involvement with these systems where they have the poten-tial to meaningfully impact rights, opportunities, or access. Additionall y, this framework does not analyze or, source_sentence: What types of data are considered sensitive according to the context provided?
sentences: Provide the public with mechanisms for appropriate and meaningful consent, access, and 
control over their data 
Use-specific consent. Consent practices should not allow for abusive surveillance practices. Where data 
collectors or automated systems seek consent, they should seek it for specific, narrow use contexts, for specif -
ic time durations, and for use by specific entities. Consent should not extend if any of these conditions change; consent should be re-acquired before using data if the use case changes, a time limit elapses, or data is trans
-, and home, work, or school environmental data); or have the reasonable potential to be used in ways that are likely to expose individuals to meaningful harm, such as a loss of privacy or financial harm due to identity theft. Data and metadata generated by or about those who are not yet legal adults is also sensitive, even if not related to a sensitive domain. Such data includes, but is not limited to, numerical, text, image, audio, or video data. “Sensitive domains” are those in which activities being conducted can cause material harms, including signifi, that data to inform the results of the automated system and why such use will not violate any applicable laws. 
In cases of high-dimensional and/or derived attributes, such justifications can be provided as overall 
descriptions of the attribute generation process and appropriateness. 
19
       
 
  SAFE AND EFFECTIVE 
SYSTEMS 
WHAT SHOULD BE EXPECTED OF AUTOMATED SYSTEMS
The expectations for automated systems are meant to serve as a blueprint for the development of additional 
technical standards and practices that are tailored for particular sectors and contexts. 
Derived data sources tracked and reviewed carefully. Data that is derived from other data through
model-index: name: SentenceTransformer based on Snowflake/snowflake-arctic-embed-m
results: task: type: information-retrieval
name: Information Retrieval
dataset: name: Unknown
type: unknown
metrics: type: cosine_accuracy@1
value: 0.7677725118483413
name: Cosine Accuracy@1
verified: no, type: cosine_accuracy@3
value: 0.8862559241706162
name: Cosine Accuracy@3
verified: no, type: cosine_accuracy@5
value: 0.9241706161137441
name: Cosine Accuracy@5
verified: no, type: cosine_accuracy@10
value: 0.981042654028436
name: Cosine Accuracy@10
verified: no, type: cosine_precision@1
value: 0.7677725118483413
name: Cosine Precision@1
verified: no, type: cosine_precision@3
value: 0.29541864139020535
name: Cosine Precision@3
verified: no, type: cosine_precision@5
value: 0.1848341232227488
name: Cosine Precision@5
verified: no, type: cosine_precision@10
value: 0.0981042654028436
name: Cosine Precision@10
verified: no, type: cosine_recall@1
value: 0.7677725118483413
name: Cosine Recall@1
verified: no, type: cosine_recall@3
value: 0.8862559241706162
name: Cosine Recall@3
verified: no, type: cosine_recall@5
value: 0.9241706161137441
name: Cosine Recall@5
verified: no, type: cosine_recall@10
value: 0.981042654028436
name: Cosine Recall@10
verified: no, type: cosine_ndcg@10
value: 0.8716745978729181
name: Cosine Ndcg@10
verified: no, type: cosine_mrr@10
value: 0.8371304445948993
name: Cosine Mrr@10
verified: no, type: cosine_map@100
value: 0.838229587684564
name: Cosine Map@100
verified: no, type: dot_accuracy@1
value: 0.7677725118483413
name: Dot Accuracy@1
verified: no, type: dot_accuracy@3
value: 0.8862559241706162
name: Dot Accuracy@3
verified: no, type: dot_accuracy@5
value: 0.9241706161137441
name: Dot Accuracy@5
verified: no, type: dot_accuracy@10
value: 0.981042654028436
name: Dot Accuracy@10
verified: no, type: dot_precision@1
value: 0.7677725118483413
name: Dot Precision@1
verified: no, type: dot_precision@3
value: 0.29541864139020535
name: Dot Precision@3
verified: no, type: dot_precision@5
value: 0.1848341232227488
name: Dot Precision@5
verified: no, type: dot_precision@10
value: 0.0981042654028436
name: Dot Precision@10
verified: no, type: dot_recall@1
value: 0.7677725118483413
name: Dot Recall@1
verified: no, type: dot_recall@3
value: 0.8862559241706162
name: Dot Recall@3
verified: no, type: dot_recall@5
value: 0.9241706161137441
name: Dot Recall@5
verified: no, type: dot_recall@10
value: 0.981042654028436
name: Dot Recall@10
verified: no, type: dot_ndcg@10
value: 0.8716745978729181
name: Dot Ndcg@10
verified: no, type: dot_mrr@10
value: 0.8371304445948993
name: Dot Mrr@10
verified: no, type: dot_map@100
value: 0.838229587684564
name: Dot Map@100
verified: no
Likes: 0 | All-time downloads: 172
Created: 2024-09-23 21:08:25