Triple
T25308375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Child Support Automation System |
E634541
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | child support case management system |
C31304
|
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 support case management system Context triple: [California Child Support Automation System, instanceOf, child support case management system]
-
A.
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.
-
B.
case management system
chosen
A case management system is a software application that organizes, tracks, and coordinates all information, tasks, and workflows related to individual cases or client matters throughout their lifecycle.
-
C.
family court system
The family court system is a specialized branch of the judiciary that resolves legal disputes and issues related to family relationships, such as divorce, child custody, support, and protection from abuse.
-
D.
family management system
A family management system is a centralized platform that helps households coordinate schedules, tasks, finances, and communication to streamline daily family life and responsibilities.
-
E.
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.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:25 p.m.