Triple
T23230515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elsene |
E581141
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sub-municipal entity of Brussels-Capital Region |
C19391
|
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: sub-municipal entity of Brussels-Capital Region Context triple: [Elsene, instanceOf, sub-municipal entity of Brussels-Capital Region]
-
A.
sub-municipality of Brussels
chosen
A sub-municipality of Brussels is a smaller administrative or statistical division within one of the 19 municipalities of the Brussels-Capital Region, typically used for local governance, planning, or demographic purposes.
-
B.
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.
-
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.
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.
Count of Brussels
The Count of Brussels is a noble title historically associated with the governance and feudal lordship of the city and surrounding region of Brussels within the medieval Low Countries.
- 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_69e246043c48819089bae72c9a9c306c |
completed | April 17, 2026, 2:39 p.m. |
Created at: April 17, 2026, 4:09 p.m.