Triple
T25036203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia Juvenile Code |
E626983
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | child welfare statute |
C29255
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: child welfare statute Context triple: [Georgia Juvenile Code, instanceOf, child welfare statute]
-
A.
child protection statute
chosen
A child protection statute is a law that establishes duties, standards, and procedures to prevent abuse, neglect, and exploitation of minors and to ensure their safety and well-being.
-
B.
child welfare legal unit
A child welfare legal unit is a specialized team within a public or private agency that provides legal representation, advice, and advocacy in cases involving the protection, placement, and rights of children and families in the child welfare system.
-
C.
child rights law
Child rights law is the body of legal principles, statutes, and international norms that recognize, protect, and enforce the specific rights and best interests of individuals under 18 in all aspects of their lives.
-
D.
child protective services agency
A child protective services agency is a government or authorized organization responsible for investigating reports of child abuse or neglect and ensuring the safety, welfare, and permanency of children through protective interventions and support services.
-
E.
child protection mechanism
A child protection mechanism is a system of policies, procedures, and tools designed to prevent, detect, and respond to abuse, neglect, or exploitation of children, ensuring their safety and well-being.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:08 a.m.