Triple
T25159258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Child Protection – Information Sharing |
E626396
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | safeguarding children programme |
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: safeguarding children programme Context triple: [Child Protection – Information Sharing, instanceOf, safeguarding children programme]
-
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 care subsidy program
A child care subsidy program is a public or private initiative that provides financial assistance to eligible families to help cover the cost of child care, enabling parents or guardians to work, attend school, or participate in training.
-
D.
programme of work
A programme of work is a structured, time-bound collection of related tasks and activities organized to achieve specific objectives or deliver defined outcomes.
-
E.
child protection statute
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.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:31 a.m.