Triple
T25308376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Child Support Automation System |
E634541
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | statewide information system |
C224
|
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: statewide information system Context triple: [California Child Support Automation System, instanceOf, statewide information system]
-
A.
state system
A state system is a structured framework in which distinct political entities (states) interact under shared norms, rules, and institutions that regulate their behavior and relationships.
-
B.
legislative information system
A legislative information system is a digital platform that collects, manages, tracks, and provides access to legislative documents, processes, and activities to support lawmakers, staff, and the public.
-
C.
statewide school system
A statewide school system is a coordinated network of public educational institutions, policies, and administrative bodies that operate under a unified state authority to provide standardized education across all regions within the state.
-
D.
NIH information system
An NIH information system is an integrated digital platform that manages, stores, and facilitates secure access to biomedical research data, administrative records, and operational information across the National Institutes of Health.
-
E.
information system
chosen
An information system is an organized combination of people, processes, data, and technology designed to collect, process, store, and distribute information to support decision-making and control in an organization.
- 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.