Triple
T36525746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rules of Procedure of the Senate |
E900297
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | source of parliamentary law in Poland |
C64960
|
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: source of parliamentary law in Poland Context triple: [Rules of Procedure of the Senate, instanceOf, source of parliamentary law in Poland]
-
A.
Polish law
Polish law is the national legal system of Poland, based primarily on civil law traditions, that regulates the rights, duties, and relationships of individuals, organizations, and public authorities within the Polish state.
-
B.
Ukrainian legislation
Ukrainian legislation is the system of legal norms, acts, and regulations adopted by competent Ukrainian authorities that govern social relations, define rights and obligations, and establish the legal framework of the state.
-
C.
foundational law of the Polish–Lithuanian Commonwealth
A foundational law of the Polish–Lithuanian Commonwealth is a core constitutional act or legal principle that defined the political structure, rights, and governance of the union between Poland and Lithuania.
-
D.
Polish parliamentary constituency
A Polish parliamentary constituency is a geographically defined electoral district in Poland from which representatives are elected to the national parliament (Sejm and/or Senate).
-
E.
parliament of Lithuania
The parliament of Lithuania, known as the Seimas, is a unicameral legislative body responsible for enacting laws, approving the budget, overseeing the government, and shaping national policy.
- F. None of above. chosen
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_69f76e5eedb88190a393b8c623f71dd7 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.