Triple
T25308377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Child Support Automation System |
E634541
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government technology platform |
C29061
|
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: government technology platform Context triple: [California Child Support Automation System, instanceOf, government technology platform]
-
A.
government operation
Government operation is the coordinated set of activities, processes, and procedures through which a government implements laws, delivers public services, and manages public resources to achieve policy objectives.
-
B.
government affairs intelligence platform
A government affairs intelligence platform is a system that aggregates, analyzes, and visualizes legislative, regulatory, and political data to help organizations monitor policy developments and inform advocacy strategies.
-
C.
civic technology company
A civic technology company is an organization that designs and deploys digital tools and platforms to improve public services, enhance government transparency, and increase citizen engagement in civic processes.
-
D.
e-government program
chosen
An e-government program is an organized initiative that uses digital technologies to deliver public services, enhance government operations, and improve interaction between government, citizens, and businesses.
-
E.
Supply-side platform
A supply-side platform is a technology system that helps digital publishers manage, optimize, and automate the selling of their advertising inventory across multiple ad exchanges and demand sources.
- 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.