Triple
T13742536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Provincial Synod of Province 6 |
E330120
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional legislative assembly |
C125
|
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: regional legislative assembly Context triple: [Provincial Synod of Province 6, instanceOf, regional legislative assembly]
-
A.
regional assembly
A regional assembly is a deliberative body composed of representatives from a specific geographic area that debates, formulates, and sometimes enacts policies or regulations affecting that region.
-
B.
subnational legislature
chosen
A subnational legislature is a lawmaking body that operates below the national level—such as a state, provincial, or regional assembly—responsible for creating and overseeing laws and policies within its specific territorial jurisdiction.
-
C.
regional legislature of Russia
A regional legislature of Russia is a representative elected body at the subnational (federal subject) level that enacts laws, approves budgets, and oversees executive authorities within its respective region in accordance with the Russian Federation’s constitutional framework.
-
D.
legislative body
A legislative body is an organized group of elected or appointed representatives empowered to create, amend, and repeal laws and oversee government policy within a political system.
-
E.
regional legislation
Regional legislation comprises the laws, regulations, and legal frameworks enacted by subnational authorities (such as states, provinces, or regions) to govern matters within their territorial jurisdiction.
- 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:55 p.m.