Triple
T21779342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bundeseisenbahnvermögen |
E537670
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German federal institution |
C41981
|
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: German federal institution Context triple: [Bundeseisenbahnvermögen, instanceOf, German federal institution]
-
A.
federal body of Germany
chosen
A federal body of Germany is an institution established by the German constitution or federal law that exercises legislative, executive, or judicial authority at the national level within the Federal Republic of Germany.
-
B.
federal agency of Germany
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.
German federal government
The German federal government is the central executive authority of the Federal Republic of Germany, consisting primarily of the Federal Chancellor and federal ministers, responsible for implementing laws and directing national policy.
-
D.
Prussian state institution
A Prussian state institution is a formal governmental body or organization established by the Kingdom of Prussia to administer public affairs, implement state policies, and maintain social order within its territories.
-
E.
constitutional organ of Germany
A constitutional organ of Germany is a state institution explicitly established and empowered by the German Basic Law to perform core governmental functions within the federal constitutional order.
- 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_69e0c470759c819094a215757113562b |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:52 p.m.