Triple
T1762162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgian Ministry of Defence |
E38680
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal government department |
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: federal government department Context triple: [Belgian Ministry of Defence, instanceOf, federal government department]
-
A.
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.
-
B.
federation of government agencies
A federation of government agencies is a collaborative structure in which multiple semi-autonomous public organizations coordinate policies, resources, and operations to achieve shared governmental objectives while retaining their individual mandates.
-
C.
non-ministerial government department
A non-ministerial government department is a public body that carries out governmental functions independently of direct ministerial control, typically to ensure impartiality or regulatory neutrality.
-
D.
United States federal government agency
A United States federal government agency is an organization established by federal law or executive authority to implement, administer, and enforce specific national policies, programs, and regulations on behalf of the U.S. government.
-
E.
federal institution
A federal institution is an organization established and operated by a national government to implement, regulate, or support public policies and services across the entire country.
- 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_69a8862d562481908d7025a1c1f67c0d |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:31 p.m.