Triple
T18520182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CyberTipline |
E452563
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | child protection hotline |
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 protection hotline Context triple: [CyberTipline, instanceOf, child protection hotline]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
children’s charity
A children’s charity is a nonprofit organization dedicated to improving the well-being, safety, health, and future opportunities of children, particularly those who are vulnerable or disadvantaged.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:37 a.m.