Triple
T6520197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss Financial Market Supervisory Authority |
E148360
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Swiss federal authority |
C15238
|
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: Swiss federal authority Context triple: [Swiss Financial Market Supervisory Authority, instanceOf, Swiss federal authority]
-
A.
Swiss federal law
Swiss federal law is the body of legal rules and principles enacted or recognized at the national level in Switzerland that uniformly govern matters within the competence of the Swiss Confederation across all cantons.
-
B.
federal office of Switzerland
chosen
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.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 1:45 p.m.