Triple
T8883031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bavarian State Chancellery |
E211456
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state chancellery |
C3463
|
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: state chancellery Context triple: [Bavarian State Chancellery, instanceOf, state chancellery]
-
A.
chancellery position
A chancellery position is an official role within a governmental or institutional chancellery responsible for high-level administrative, legal, or executive functions supporting the head of the organization.
-
B.
ministry of a German state
A ministry of a German state is a top-level governmental department within a federal state (Land) responsible for formulating and implementing policy in a specific sector, such as education, finance, or justice, under the authority of the state government.
-
C.
colonial office
A colonial office is a governmental department or administrative body responsible for managing and overseeing the affairs, policies, and governance of a colony or group of colonies on behalf of a colonial power.
-
D.
state government office
chosen
A state government office is an administrative entity within a state’s governmental structure responsible for implementing specific public policies, services, and regulatory functions under the authority of state law.
-
E.
federal office of Switzerland
A federal office of Switzerland is an administrative unit within a federal department responsible for implementing national policies, managing specific public functions, and supporting the Swiss Federal Council’s decisions in its designated domain.
- 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_69ca838f9e20819096ab1f236a70381a |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:53 p.m.