Triple
T4082070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Title V – The Federal Government |
E87498
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | section of the Constitution of Belgium |
C9668
|
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: section of the Constitution of Belgium Context triple: [Title V – The Federal Government, instanceOf, section of the Constitution of Belgium]
-
A.
federal entity of Belgium
A federal entity of Belgium is one of the constitutionally recognized components of the Belgian state—either a region or a community—endowed with its own government, parliament, and specific legislative and administrative powers.
-
B.
Belgian federal government
chosen
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.
province of Belgium
A province of Belgium is a primary administrative subdivision of the country, situated between the federal regions and municipalities, with its own local government and competencies.
-
D.
district of Belgium
A district of Belgium is an administrative subdivision within a province that groups several municipalities for purposes such as judicial organization, electoral arrangements, and certain governmental services.
-
E.
constitutional provision
A constitutional provision is a specific, authoritative rule or principle written into a constitution that defines the structure, powers, and limits of government and the rights of individuals.
- 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:39 p.m.