Triple
T37921899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anordnung über die deutschen Flaggen |
E945985
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | deutsche Rechtsvorschrift |
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: deutsche Rechtsvorschrift Context triple: [Anordnung über die deutschen Flaggen, instanceOf, deutsche Rechtsvorschrift]
-
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.
Dutch statute
A Dutch statute is a formal written law enacted by the Dutch legislature (Staten-Generaal) and, where required, sanctioned and promulgated by the government, forming part of the binding legal framework of the Netherlands.
-
D.
legal code of Bavaria
The legal code of Bavaria is the comprehensive body of laws, regulations, and judicial principles that govern civil, criminal, administrative, and constitutional matters within the German state of Bavaria.
-
E.
deutsche Organisation
Eine deutsche Organisation ist eine in Deutschland ansässige, rechtlich strukturierte Einheit (z.B. Verein, Unternehmen, Behörde oder Stiftung), die bestimmte Ziele verfolgt und nach deutschen Gesetzen handelt.
- 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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.