Triple
T27120326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ministry of Ecclesiastical Affairs of Denmark |
E686977
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Danish government ministry |
C3428
|
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: Danish government ministry Context triple: [Ministry of Ecclesiastical Affairs of Denmark, instanceOf, Danish government ministry]
-
A.
Norwegian government agency
A Norwegian government agency is a public sector organization established by the Norwegian state to implement laws, deliver public services, and administer specific policy areas on behalf of the government.
-
B.
government ministry
chosen
A government ministry is a specialized administrative department within a government, headed by a minister, responsible for formulating and implementing public policies in a specific sector such as health, education, or finance.
-
C.
Danish royal office
A Danish royal office is an institutional entity within the Danish monarchy responsible for supporting, administering, and representing the official duties and functions of the royal family.
-
D.
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.
-
E.
English government ministry
An English government ministry is a central executive department responsible for developing and implementing public policy and administering specific areas of government activity within England.
- 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_69ef148c2b588190afc15b529f7af845 |
completed | April 27, 2026, 7:47 a.m. |
Created at: April 27, 2026, 8:59 a.m.