Triple
T826171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Financial Policy Committee |
E17856
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bank of England body |
C3617
|
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: Bank of England body Context triple: [Financial Policy Committee, instanceOf, Bank of England body]
-
A.
British government department
A British government department is an administrative unit of the UK government responsible for developing and implementing public policy and delivering specific services within a defined area of national governance.
-
B.
United Kingdom government department
A United Kingdom government department is a major administrative unit of the UK central government responsible for developing and implementing public policy and delivering specific services within a defined area of national governance.
-
C.
United Kingdom ministry
A United Kingdom ministry is a central government department, headed by a secretary of state or minister, responsible for formulating and implementing public policy within a specific area of national governance.
-
D.
British organisation
chosen
A British organisation is an entity based in or primarily operating within the United Kingdom, formed by individuals or groups to pursue specific social, cultural, economic, or political objectives under UK legal and regulatory frameworks.
-
E.
British intelligence agency
A British intelligence agency is a government organization responsible for gathering, analyzing, and acting on information to protect the United Kingdom’s national security and interests at home and abroad.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:38 p.m.