Triple
T38073381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bundesministerium |
E950644
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Verwaltungsorgan |
C3213
|
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: Verwaltungsorgan Context triple: [Bundesministerium, instanceOf, Verwaltungsorgan]
-
A.
public administration body
chosen
A public administration body is an organization within the public sector responsible for implementing laws, delivering public services, and managing governmental policies and resources on behalf of the state and its citizens.
-
B.
Verwaltungseinheit
Eine Verwaltungseinheit ist eine organisatorische Einheit innerhalb einer öffentlichen oder privaten Institution, die für die Erfüllung bestimmter Verwaltungsaufgaben und die Umsetzung von Richtlinien in einem abgegrenzten Zuständigkeitsbereich verantwortlich ist.
-
C.
administrative organ of an international organization
An administrative organ of an international organization is a permanent body responsible for managing the organization’s day-to-day operations, implementing its decisions, and providing support services to its other organs and member states.
-
D.
governmental organization
A governmental organization is a formally structured public entity established by a government to create, implement, or enforce laws, policies, and services for a specific jurisdiction or public purpose.
-
E.
administrative establishment
An administrative establishment is an organization or facility responsible for managing, coordinating, and executing governmental or institutional policies, procedures, and services.
- 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.