Triple
T20453838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German Fiscal Code |
E501723
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal law of Germany |
C7727
|
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 law of Germany Context triple: [German Fiscal Code, instanceOf, federal law of Germany]
-
A.
German federal statute
chosen
A German federal statute is a legally binding rule enacted by the federal legislature of Germany that applies uniformly across all federal states.
-
B.
Prussian law
Prussian law refers to the body of legal principles, statutes, and judicial practices that governed the Kingdom of Prussia, characterized by a strong centralized authority, codification efforts like the Allgemeines Landrecht, and an emphasis on bureaucratic administration and social order.
-
C.
Austrian federal law
Austrian federal law is the body of legal norms enacted at the national level in Austria that governs matters within the competence of the federal state, such as constitutional structure, civil and criminal law, and nationwide administrative regulations.
-
D.
politics of a federal state of Germany
The politics of a federal state of Germany encompass the structures, processes, and interactions of its state-level institutions, parties, and actors within the framework of Germany’s federal system and constitutional order.
-
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_69e0b4ad4940819098cf2ff6413574e5 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:32 a.m.