Triple
T7966205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landesministerien für Raumordnung und Landesplanung |
E185213
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Landesministerium |
C19067
|
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: Landesministerium Context triple: [Landesministerien für Raumordnung und Landesplanung, instanceOf, Landesministerium]
-
A.
ministry of a German state
chosen
A ministry of a German state is a top-level governmental department within a federal state (Land) responsible for formulating and implementing policy in a specific sector, such as education, finance, or justice, under the authority of the state government.
-
B.
government ministry
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.
provincial government agency
A provincial government agency is a public-sector organization established by a provincial authority to implement policies, deliver services, and regulate activities within its jurisdiction.
-
D.
federal ministerial office
A federal ministerial office is a governmental entity headed by a federal minister, responsible for developing, implementing, and overseeing policies and administrative functions within a specific national portfolio or sector.
-
E.
interior ministry
The interior ministry is a government department responsible for domestic affairs, including internal security, public administration, civil registration, and often oversight of police and emergency 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_69ca8297699481909b75a405f01e03af |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:12 p.m.