Triple
T1900137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brussels-Capital Region |
E37672
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | region of Europe |
C9961
|
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: region of Europe Context triple: [Brussels-Capital Region, instanceOf, region of Europe]
-
A.
country in Eastern Europe
A country in Eastern Europe is a sovereign state located in the eastern part of the European continent, typically characterized by shared historical ties, cultural influences, and geopolitical connections within this region.
-
B.
European country
A European country is a sovereign state located wholly or partly on the continent of Europe, defined by its own government, territory, population, and internationally recognized borders.
-
C.
Central European country
A Central European country is a sovereign state located in the central part of the European continent, typically characterized by its landlocked or semi-landlocked position, shared historical and cultural ties, and membership or close association with European political and economic institutions.
-
D.
country in Central Europe
A country in Central Europe is a sovereign state located in the central part of the European continent, typically characterized by its landlocked or partially landlocked position and cultural, historical, and economic ties with neighboring European nations.
-
E.
region of Germany
A region of Germany is a geographically and culturally distinct area within the country, often defined by historical boundaries, administrative divisions, or shared economic and social characteristics.
- 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_69a8861be7148190a680937ec451a304 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:35 p.m.