Triple
T35378927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rules on budgetary procedures |
E1022590
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | section of the European Parliament Rules of Procedure |
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: section of the European Parliament Rules of Procedure Context triple: [Rules on budgetary procedures, instanceOf, section of the European Parliament Rules of Procedure]
-
A.
European Parliament rule
A European Parliament rule is a formal provision or directive that governs the internal procedures, decision-making processes, and conduct of Members and bodies within the European Parliament.
-
B.
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.
-
C.
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.
-
D.
organ of the European Parliament
An organ of the European Parliament is an internal institutional body or structure, such as a committee, bureau, or secretariat, that performs specific legislative, administrative, or organizational functions to support the Parliament’s work.
-
E.
section of the Belgian Constitution
A section of the Belgian Constitution is a distinct, numbered subdivision that groups together related constitutional provisions governing specific aspects of the Belgian state, its institutions, or fundamental rights.
- 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.