Triple
T10866875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GOV.UK Design System |
E256552
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government design system |
C11445
|
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 design system Context triple: [GOV.UK Design System, instanceOf, government design system]
-
A.
government visual identity system
chosen
A government visual identity system is a standardized set of design elements—such as logos, colors, typography, and layout rules—that consistently represent a government’s authority, values, and services across all communications and media.
-
B.
system of government agencies
A system of government agencies is an organized network of public institutions, each with specific legal authority and responsibilities, that collectively implement laws, deliver services, and administer public policy on behalf of the state.
-
C.
state design organization
A state design organization is a government-affiliated entity that applies design methods and systems thinking to improve public services, policies, and citizen experiences.
-
D.
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.
-
E.
governing blueprint
A governing blueprint is a high-level, authoritative plan or framework that defines the structure, rules, and guiding principles by which a system, organization, or society is directed and managed.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:20 p.m.