Triple

T16755980
Position Surface form Disambiguated ID Type / Status
Subject Belgian Judicial Code E407206 entity
Predicate instanceOf P0 FINISHED
Object Belgian federal law C37980 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: Belgian federal law
Context triple: [Belgian Judicial Code, instanceOf, Belgian federal law]
  • A. 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.
  • B. Belgian federal government
    The Belgian federal government is the central governing authority of Belgium, responsible for national policy areas such as defense, justice, social security, and federal finance, operating within a complex federal system that shares powers with regional and community governments.
  • 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. Swiss federal law
    Swiss federal law is the body of legal rules and principles enacted or recognized at the national level in Switzerland that uniformly govern matters within the competence of the Swiss Confederation across all cantons.
  • E. section of the Belgian Constitution
    A section of the Belgian Constitution is a distinct, numbered subdivision that groups together related constitutional provisions governing specific aspects of the Belgian state, its institutions, or fundamental rights.
  • F. None of above. chosen

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_69d8839174188190909f190097207065 completed April 10, 2026, 4:58 a.m.
Created at: April 10, 2026, 5:21 a.m.