Triple
T826122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monetary Policy Committee |
E17855
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | committee of the Bank of England |
C308
|
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: committee of the Bank of England Context triple: [Monetary Policy Committee, instanceOf, committee of the Bank of England]
-
A.
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.
-
B.
board committee
A board committee is a small, specialized group of board members delegated specific responsibilities to support the board’s governance, oversight, and decision-making functions.
-
C.
governing council
chosen
A governing council is a formal body of appointed or elected individuals responsible for making high-level decisions, setting policies, and providing oversight for an organization, community, or institution.
-
D.
government committee
A government committee is a formally established group of officials or representatives tasked with studying specific issues, developing recommendations, and overseeing particular areas of public policy or administration.
-
E.
Government of the United Kingdom
The Government of the United Kingdom is the central executive authority responsible for implementing laws, formulating national policy, and administering public services across the UK under the constitutional monarchy and parliamentary system.
- 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.