Triple
T9314603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Network and Information Systems Regulations |
E224086
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UK statutory instrument |
C6135
|
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 statutory instrument Context triple: [Network and Information Systems Regulations, instanceOf, UK statutory instrument]
-
A.
Act of Parliament of the United Kingdom
An Act of Parliament of the United Kingdom is a formal law enacted by the UK Parliament, comprising the House of Commons, the House of Lords, and the monarch, which has legal force throughout its applicable jurisdictions.
-
B.
legal instrument of the Parliament of the United Kingdom
chosen
A legal instrument of the Parliament of the United Kingdom is a formal written law or regulation, such as an Act or statutory instrument, enacted or authorized by Parliament to create, modify, or repeal legal rights and obligations within the UK.
-
C.
Welsh statute
A Welsh statute is a law formally enacted by the Senedd (Welsh Parliament) that applies within Wales, often addressing devolved matters such as health, education, and local government.
-
D.
Act of the Scottish Parliament
An Act of the Scottish Parliament is a primary law formally enacted by the Scottish Parliament within the scope of its devolved legislative powers in Scotland.
-
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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:37 p.m.