Triple
T8225897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brussels Airport Company |
E192171
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | company based in Belgium |
C9186
|
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: company based in Belgium Context triple: [Brussels Airport Company, instanceOf, company based in Belgium]
-
A.
Dutch company
A Dutch company is a business entity established under the laws of the Netherlands, typically registered with the Dutch Chamber of Commerce and subject to Dutch corporate, tax, and regulatory frameworks.
-
B.
European company
chosen
A European company is a business entity legally registered and operating within one or more countries of Europe, subject to European and relevant national regulations, markets, and cultural contexts.
-
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.
British-Dutch company
A British-Dutch company is a business organization that is jointly rooted in and typically operates under the corporate, legal, and tax frameworks of both the United Kingdom and the Netherlands, often with dual headquarters or a historically binational structure.
-
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.
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_69ca82c9a8ac81908b011c38698456e4 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:45 p.m.