Triple
T31021325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PRR |
E790456
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United Kingdom regulation |
C59931
|
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: United Kingdom regulation Context triple: [PRR, instanceOf, United Kingdom regulation]
-
A.
United Kingdom statutory rules
United Kingdom statutory rules are legally binding regulations made under the authority of Acts of Parliament, detailing how those Acts are to be implemented and applied in practice.
-
B.
United Kingdom Defence Regulation
United Kingdom Defence Regulation is a conceptual class representing the body of legal rules, statutory instruments, and administrative measures enacted by the UK government to organize, control, and direct national defence activities, including military operations, security protocols, and wartime emergency powers.
-
C.
United Kingdom standard
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.
-
D.
place in the United Kingdom
A place in the United Kingdom is any geographically defined location—such as a city, town, village, or landmark—situated within the political boundaries of England, Scotland, Wales, or Northern Ireland.
-
E.
UK financial regulation
UK financial regulation is the framework of laws, rules, and supervisory practices that govern financial markets, institutions, and services in the United Kingdom to ensure stability, integrity, and consumer protection.
- F. None of above. chosen
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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:58 p.m.