Triple
T26367726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Vlaamse Waterweg nv |
E660388
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Flemish public company |
C51464
|
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: Flemish public company Context triple: [De Vlaamse Waterweg nv, instanceOf, Flemish public company]
-
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.
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.
-
C.
European company
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.
-
D.
Belgian federal public service
A Belgian federal public service is a national-level administrative body responsible for implementing federal government policies, delivering public services, and supporting the functioning of the Belgian state across its various domains of competence.
-
E.
Dutch organization
A Dutch organization is an entity established in the Netherlands, operating under Dutch law to pursue specific economic, social, cultural, or governmental objectives.
- 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_69ee8126d52c8190bc0b34337c2c9aa8 |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 10:56 p.m.