Triple
T35378780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rules on parliamentary committees |
E1022587
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | parliamentary rule |
C1861
|
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 rule Context triple: [Rules on parliamentary committees, instanceOf, parliamentary rule]
-
A.
parliamentary rules
chosen
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.
parliamentary scheme
A parliamentary scheme is a structured format for debate or governance in which participants follow defined roles, procedures, and rules to propose, discuss, and decide on motions or policies.
-
C.
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.
-
D.
parliamentary representation system
A parliamentary representation system is a political framework in which citizens elect representatives to a legislative body that forms or supports the government, typically reflecting party strength in proportion to votes received.
-
E.
parliamentary co-principality
A parliamentary co-principality is a political system in which two or more co-equal princes or heads of state share sovereignty under a constitutional framework where a representative parliament holds primary legislative authority.
- 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_69f76df28d8c819089f2c5799fe7d079 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.