Triple
T32908231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Provincial Sejm in Posen |
E841799
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional representative assembly |
C21157
|
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 representative assembly Context triple: [Provincial Sejm in Posen, instanceOf, regional representative assembly]
-
A.
regional assembly
chosen
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.
regional electoral body
A regional electoral body is an organization responsible for administering, supervising, and ensuring the integrity of elections within a specific subnational geographic area.
-
C.
regional representative group
A regional representative group is an organized body of individuals chosen or appointed to advocate for and make decisions on behalf of stakeholders within a specific geographic area.
-
D.
regional committee
A regional committee is a group of appointed or elected representatives from a specific geographic area who collaborate to make decisions, coordinate activities, and provide governance or oversight on issues affecting that region.
-
E.
association of regional parliaments
An association of regional parliaments is a collaborative organization that brings together legislative bodies from different regions to coordinate policies, share best practices, and represent common interests at broader national or international levels.
- 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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:19 a.m.