Triple
T14504898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wasserstraßen- und Schifffahrtsverwaltung des Bundes |
E340239
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bundesoberbehörde |
C4912
|
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: Bundesoberbehörde Context triple: [Wasserstraßen- und Schifffahrtsverwaltung des Bundes, instanceOf, Bundesoberbehörde]
-
A.
ministry of a German state
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.
federal agency of Germany
chosen
A federal agency of Germany is a governmental body operating at the national level, responsible for implementing federal laws, policies, and administrative tasks within its designated area of competence.
-
C.
federal office of Switzerland
A federal office of Switzerland is an administrative unit within a federal department responsible for implementing national policies, managing specific public functions, and supporting the Swiss Federal Council’s decisions in its designated domain.
-
D.
bureau-level office
A bureau-level office is an organizational unit within a larger department or agency that operates at the bureau tier, managing specialized programs, policies, or services under that bureau’s authority.
-
E.
directorate-general
A directorate-general is a major administrative division within a government or large organization, typically responsible for a specific policy area or function and headed by a director-general.
- 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:21 a.m.