Triple
T35309759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | executive board of Greater Poland Voivodeship |
E1019735
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collective executive body |
C172
|
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: collective executive body Context triple: [executive board of Greater Poland Voivodeship, instanceOf, collective executive body]
-
A.
governing body
chosen
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
B.
cabinet-level body
A cabinet-level body is a high-ranking executive group, typically composed of heads of major government departments and key advisors, that assists a head of state or government in making and implementing national policy decisions.
-
C.
secretariat-type body
A secretariat-type body is an administrative organization that provides ongoing coordination, support, and implementation services for a larger governing or decision-making entity.
-
D.
collective political entity
A collective political entity is an organized group of individuals or communities that exercises or claims shared authority, representation, and decision-making power within a defined political framework.
-
E.
senior leadership body
A senior leadership body is a group of high-level executives or officials responsible for setting strategic direction, making key organizational decisions, and overseeing overall performance and governance.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.