Triple
T16755933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Council of Justice of Belgium |
E407205
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public body of Belgium |
C37979
|
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: public body of Belgium Context triple: [High Council of Justice of Belgium, instanceOf, public body of Belgium]
-
A.
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.
-
B.
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.
-
C.
region of Belgium
A region of Belgium is a first-level administrative division with its own government and competencies, such as Flanders, Wallonia, or the Brussels-Capital Region.
-
D.
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.
-
E.
municipality of Belgium
A municipality of Belgium is the smallest administrative division in the country, governed by a local council and mayor, responsible for providing public services and local regulations within its defined territory.
- 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.