Skip to content

Commit 4f3d0d2

Browse files
committed
Add benefit rules prompt
This didn't provide useful results right away though, had to correct it throughout the conversation flow. But this was a good start.
1 parent 38c87bd commit 4f3d0d2

File tree

1 file changed

+109
-0
lines changed

1 file changed

+109
-0
lines changed

sozialplattform/chatgpt_prompts.txt

+109
Original file line numberDiff line numberDiff line change
@@ -90,3 +90,112 @@ ff:aufenthaltsort-ao-innerhalb a ff:AnswerOption ; rdfs:label "innerhalb Deutsch
9090
-----
9191

9292
Does this make sense? Can I share more JSON definitions for you to transform them to SHACL following the examples I gave you?
93+
94+
95+
------------------------------------------------------------
96+
BENEFIT RULES
97+
------------------------------------------------------------
98+
99+
I would like your help in translating rules from a JSON format to a SHACL format. I have done this transformation once manually and would like you to apply the same pattern to more JSON rules. However, to interpret this correctly, I need to supply you with a definition file of the data fields in use. I uploaded it together with this message.
100+
101+
This is the example transformation:
102+
103+
JSON:
104+
105+
[
106+
{
107+
"questionKey": "Aufenthaltsort",
108+
"type": "singleSelect",
109+
"operator": "equals",
110+
"expectedValue": "innerhalb",
111+
"rules": []
112+
},
113+
{
114+
"questionKey": "Aufenthaltsort",
115+
"type": "singleSelect",
116+
"operator": "equalsNot",
117+
"expectedValue": "außerhalb",
118+
"rules": []
119+
},
120+
{
121+
"questionKey": "Geburtsdatum",
122+
"type": "date",
123+
"modifier": "Pensionable",
124+
"operator": "equals",
125+
"expectedValue": "false",
126+
"rules": []
127+
},
128+
{
129+
"questionKey": "Erwerbsfähig_neu",
130+
"type": "singleOption",
131+
"operator": "equalsNot",
132+
"expectedValue": "nein >6 Monate",
133+
"rules": []
134+
},
135+
{
136+
"questionKey": "Erwerbsfähig_neu",
137+
"type": "singleOption",
138+
"operator": "equals",
139+
"expectedValue": "nein <6 Monate",
140+
"rules": []
141+
},
142+
{
143+
"questionKey": "Beruf_neu",
144+
"type": "singleOption",
145+
"operator": "equalsNot",
146+
"expectedValue": "ALG",
147+
"rules": []
148+
},
149+
{
150+
"questionKey": "Einkommen_neu",
151+
"type": "multiOption",
152+
"operator": "containsNot",
153+
"expectedValue": "ALG",
154+
"rules": []
155+
},
156+
{
157+
"questionKey": "Einkommen_neu",
158+
"type": "multiOption",
159+
"operator": "containsNot",
160+
"expectedValue": "ALG II",
161+
"rules": []
162+
}
163+
]
164+
165+
---
166+
167+
SHACL:
168+
169+
ff:MainPersonShape a sh:NodeShape, ff:EligibilityConstraint ;
170+
sh:targetClass ff:Citizen ;
171+
sh:property [
172+
sh:path ff:aufenthaltsort ;
173+
sh:minCount 1 ;
174+
sh:hasValue ff:aufenthaltsort-ao-innerhalb ;
175+
] ;
176+
sh:property [
177+
sh:path ff:pensionable ;
178+
sh:minCount 1 ;
179+
sh:hasValue false ;
180+
] ;
181+
sh:property [
182+
sh:path ff:erwerbsfaehig_neu ;
183+
sh:minCount 1 ;
184+
sh:hasValue ff:erwerbsfaehig_neu-ao-nein-weniger-6-monate ;
185+
] ;
186+
sh:property [
187+
sh:path ff:beruf_neu ;
188+
sh:minCount 1 ;
189+
sh:not [
190+
sh:hasValue ff:beruf_neu-ao-alg ;
191+
] ;
192+
] ;
193+
sh:property [
194+
sh:path ff:einkommen_neu ;
195+
sh:minCount 1 ;
196+
sh:not [
197+
sh:in (ff:einkommen_neu-ao-alg ff:einkommen_neu-ao-alg-ii) ;
198+
] ;
199+
] .
200+
201+
Does this make sense? Can I provide you with the next set of JSON rules for you to transform it to SHACL?

0 commit comments

Comments
 (0)