Triple
T10503846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stolen Generations policies |
E247735
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | child removal policy |
C26829
|
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 removal policy Context triple: [Stolen Generations policies, instanceOf, child removal policy]
-
A.
child protection mechanism
chosen
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.
-
B.
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.
-
C.
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.
-
D.
child support agency
A child support agency is an organization that helps establish, enforce, and manage financial and related support obligations for children, typically by working with parents, courts, and other authorities.
-
E.
child
A child is a young human being in the early stages of physical, cognitive, emotional, and social development, typically dependent on adults for care and guidance.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:26 p.m.