Triple
T10867171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Technology Code of Practice |
E256555
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UK government standard |
C27513
|
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: UK government standard Context triple: [Technology Code of Practice, instanceOf, UK government standard]
-
A.
United Kingdom standard
chosen
A United Kingdom standard is an officially recognized specification or guideline that defines consistent technical, safety, or quality requirements for products, services, or processes within the UK.
-
B.
UK government unit
A UK government unit is an organizational entity within the United Kingdom’s system of public administration that carries out specific governmental functions, services, or policy responsibilities under the authority of a department or minister.
-
C.
English government ministry
An English government ministry is a central executive department responsible for developing and implementing public policy and administering specific areas of government activity within England.
-
D.
UK public authority
A UK public authority is an organization or body in the United Kingdom that carries out public functions or services and is subject to public law duties, including transparency and accountability obligations.
-
E.
British government policy statement
A British government policy statement is an official, authoritative document or announcement that sets out the UK government’s intentions, principles, and planned actions on a specific public issue or area of governance.
- 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.