Triple
T1900136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brussels-Capital Region |
E37672
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal region of Belgium |
C4635
|
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 region of Belgium Context triple: [Brussels-Capital Region, instanceOf, federal region of Belgium]
-
A.
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.
-
B.
region of Belgium
chosen
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.
-
C.
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.
-
D.
province of the Netherlands
A province of the Netherlands is a primary administrative division of the country, governed by its own provincial authorities and responsible for regional planning, infrastructure, and certain public services within its territory.
-
E.
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.
- 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_69a8861be7148190a680937ec451a304 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:35 p.m.