Triple
T15587944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eidgenössisches Departement des Innern |
E374670
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Schweizer Bundesdepartement |
C36377
|
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: Schweizer Bundesdepartement Context triple: [Eidgenössisches Departement des Innern, instanceOf, Schweizer Bundesdepartement]
-
A.
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.
-
B.
Swiss Federal Council
The Swiss Federal Council is the seven-member executive body that collectively serves as both the head of state and government of Switzerland, responsible for leading the federal administration and implementing national policy.
-
C.
chamber of the Federal Assembly of Switzerland
A chamber of the Federal Assembly of Switzerland is one of its two legislative houses—the National Council or the Council of States—responsible for debating, amending, and passing federal laws and overseeing the federal government.
-
D.
Swiss canton code
A Swiss canton code is a standardized short alphanumeric identifier used to uniquely represent each canton within Switzerland for administrative, statistical, and legal purposes.
-
E.
Swiss canton
A Swiss canton is a semi-sovereign federal state within Switzerland, possessing its own constitution, government, and legislative authority under the Swiss federal system.
- F. None of above. chosen
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_69d85cce25008190b13b52745fbd719b |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:11 a.m.