Ansh007's picture
Update config.json
9c2742b verified
raw
history blame
3.58 kB
Invalid JSON: Unexpected token ',', ...""widget": , "text"... is not valid JSON
{
"_name_or_path": "/kaggle/working/Bert_01",
"architectures": [
"BertForSequenceClassification"
],
"attention_probs_dropout_prob": 0.1,
"classifier_dropout": null,
"gradient_checkpointing": false,
"hidden_act": "gelu",
"hidden_dropout_prob": 0.1,
"hidden_size": 768,
"id2label": {
"0": "virtual assets",
"1": "guideline",
"2": "license",
"3": "transfer",
"4": "rulebook",
"5": "cft",
"6": "circular",
"7": "legal",
"8": "vasp",
"9": "operator",
"10": "transactions",
"11": "transaction",
"12": "regulator",
"13": "regulations",
"14": "dlt",
"15": "screening",
"16": "compliance",
"17": "sanctions",
"18": "monitoring",
"19": "investor protection",
"20": "cdd",
"21": "due diligence",
"22": "client",
"23": "entities",
"24": "criminal",
"25": "record keeping",
"26": "policy",
"27": "controls",
"28": "requirements",
"29": "risk assessment",
"30": "insider dealing",
"31": "policies",
"32": "suspicious transactions",
"33": "anti-bribery",
"34": "investor",
"35": "rules",
"36": "authority",
"37": "safeguard",
"38": "beneficiary information",
"39": "legislation",
"40": "reporting",
"41": "disclosure",
"42": "pep",
"43": "kyc",
"44": "oversight",
"45": "risks",
"46": "aml",
"47": "person",
"48": "code of conduct",
"49": "risk management",
"50": "travel rule",
"51": "conduct",
"52": "audit",
"53": "identity",
"54": "vasps"
},
"initializer_range": 0.02,
"intermediate_size": 3072,
"label2id": {
"aml": 46,
"anti-bribery": 33,
"audit": 52,
"authority": 36,
"beneficiary information": 38,
"cdd": 20,
"cft": 5,
"circular": 6,
"client": 22,
"code of conduct": 48,
"compliance": 16,
"conduct": 51,
"controls": 27,
"criminal": 24,
"disclosure": 41,
"dlt": 14,
"due diligence": 21,
"entities": 23,
"guideline": 1,
"identity": 53,
"insider dealing": 30,
"investor": 34,
"investor protection": 19,
"kyc": 43,
"legal": 7,
"legislation": 39,
"license": 2,
"monitoring": 18,
"operator": 9,
"oversight": 44,
"pep": 42,
"person": 47,
"policies": 31,
"policy": 26,
"record keeping": 25,
"regulations": 13,
"regulator": 12,
"reporting": 40,
"requirements": 28,
"risk assessment": 29,
"risk management": 49,
"risks": 45,
"rulebook": 4,
"rules": 35,
"safeguard": 37,
"sanctions": 17,
"screening": 15,
"suspicious transactions": 32,
"transaction": 11,
"transactions": 10,
"transfer": 3,
"travel rule": 50,
"vasp": 8,
"vasps": 54,
"virtual assets": 0
},
"layer_norm_eps": 1e-12,
"max_position_embeddings": 512,
"model_type": "bert",
"num_attention_heads": 12,
"num_hidden_layers": 12,
"pad_token_id": 0,
"position_embedding_type": "absolute",
"problem_type": "multi_label_classification",
"torch_dtype": "float32",
"transformers_version": "4.41.1",
"type_vocab_size": 2,
"use_cache": true,
"vocab_size": 30522,
"widget": ,
"text": "Where an FI employs a technological solution provided by an external party to conduct screening of virtual asset transactions and the associated wallet addresses, the FI remains responsible for discharging its AML/CFT obligations. The FI should conduct due diligence on the solution before deploying it, taking into account relevant factors such as:"
}