Triple
T2712186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standing Orders of the House of Representatives |
E59887
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | parliamentary standing orders |
C6256
|
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: parliamentary standing orders Context triple: [Standing Orders of the House of Representatives, instanceOf, parliamentary standing orders]
-
A.
parliamentary rules
Parliamentary rules are the formal procedures and guidelines that govern how legislative or deliberative bodies conduct meetings, debate, decision-making, and voting to ensure order, fairness, and efficiency.
-
B.
rules of procedure
chosen
Rules of procedure are formal guidelines that govern how decisions are proposed, discussed, and made within an organization, assembly, or legal process.
-
C.
parliamentary record
A parliamentary record is an official, authoritative written or transcribed account of the proceedings, debates, decisions, and votes that occur within a parliamentary body.
-
D.
tradition of the House of Commons of the United Kingdom
The tradition of the House of Commons of the United Kingdom encompasses the long-established customs, procedures, ceremonial practices, and unwritten conventions that shape how the lower chamber of Parliament conducts its debates, business, and interactions with the Crown and the public.
-
E.
parliamentary position
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.
- 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_69ab4ac92a088190bc74bca14038e3de |
completed | March 6, 2026, 9:44 p.m. |
Created at: March 6, 2026, 9:55 p.m.