Triple
T640222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Speaker |
E16721
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | office in the House of Lords |
C509
|
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: office in the House of Lords Context triple: [Lord Speaker, instanceOf, office in the House of Lords]
-
A.
member of the House of Lords
A member of the House of Lords is an appointed or hereditary individual who serves in the upper chamber of the UK Parliament, participating in the review, amendment, and scrutiny of legislation and public policy.
-
B.
Privy Councillor
A Privy Councillor is a senior advisor appointed to a sovereign or head of state, serving on a formal council that provides confidential counsel on matters of governance and policy.
-
C.
parliamentary position
chosen
A parliamentary position is a formal role or office held by an individual within a legislative body, encompassing specific duties, powers, and responsibilities in the conduct of parliamentary business.
-
D.
United Kingdom cabinet position
A United Kingdom cabinet position is a senior governmental role held by a minister appointed by the Prime Minister to lead a specific department or policy area and collectively make high-level executive decisions.
-
E.
ministerial department of the Government of the United Kingdom
A ministerial department of the Government of the United Kingdom is a major executive organization, led by a government minister, responsible for developing and implementing policy and delivering public services within a specific area of national 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:35 p.m.