Triple
T3710802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marshal of the Lesser Poland Voivodeship |
E81405
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional government position |
C7910
|
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 government position Context triple: [Marshal of the Lesser Poland Voivodeship, instanceOf, regional government position]
-
A.
municipal government position
A municipal government position is a role within a city or local government responsible for administering public services, implementing local policies, and managing community resources and regulations.
-
B.
public administration position
chosen
A public administration position is a role within government or public sector organizations responsible for planning, implementing, and managing policies and services that serve the public interest.
-
C.
regional administrative branch
A regional administrative branch is a localized division of a larger organization or government responsible for managing operations, implementing policies, and coordinating services within a specific geographic area.
-
D.
county government position
A county government position is a public office or role within a county’s administrative structure responsible for delivering local services, enforcing county policies, and representing the interests of county residents.
-
E.
Cabinet position
A cabinet position is a high-level government role, typically heading an executive department, appointed to advise and assist the chief executive in implementing public policy.
- 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_69ad8b1a81588190b3f27a5483bb610e |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:33 p.m.