Triple
T22437302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riksdrots |
E554659
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Swedish state office |
C31990
|
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: Swedish state office Context triple: [Riksdrots, instanceOf, Swedish state office]
-
A.
Swedish public office
chosen
A Swedish public office is a government authority or agency in Sweden responsible for implementing laws, delivering public services, and administering specific areas of public policy under national or local jurisdiction.
-
B.
Swedish government agency
A Swedish government agency is a public organization established by the Swedish state to implement laws, deliver public services, and execute policies under the direction of the government and parliament.
-
C.
Government of Sweden
The Government of Sweden is the executive branch of the Swedish state, headed by the Prime Minister and composed of ministers who collectively implement laws, manage public administration, and direct national policy under a parliamentary system.
-
D.
Swedish government cabinet
The Swedish government cabinet is the collective executive body composed of the Prime Minister and appointed ministers who lead government ministries and are responsible for implementing national policies and decisions in Sweden.
-
E.
County administrative board of Sweden
The County Administrative Board of Sweden is a regional government authority responsible for implementing national policies, coordinating state administration, and overseeing legal compliance and sustainable development within its county.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:47 p.m.