Triple
T25164685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enschede fireworks disaster |
E630139
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | disaster in the Netherlands |
C223
|
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: disaster in the Netherlands Context triple: [Enschede fireworks disaster, instanceOf, disaster in the Netherlands]
-
A.
disaster
chosen
A disaster is a sudden, disruptive event—natural or human-made—that causes significant harm to people, property, or the environment and overwhelms normal coping capacities.
-
B.
Dutch water board
A Dutch water board is a regional government body responsible for managing water levels, flood protection, water quality, and wastewater treatment within its designated area in the Netherlands.
-
C.
region of the Netherlands
A region of the Netherlands is a geographically and culturally defined area within the country, often used for administrative, historical, or socio-economic purposes.
-
D.
port of the Netherlands
A port of the Netherlands is a maritime facility located along the Dutch coastline or inland waterways that supports the docking, loading, unloading, storage, and transit of goods and passengers within national and international shipping networks.
-
E.
national monument of the Netherlands
A national monument of the Netherlands is a building, structure, or site officially designated and protected by the Dutch government for its exceptional cultural, historical, or architectural significance.
- 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_69e75a87c9b88190ab60731902a99750 |
completed | April 21, 2026, 11:07 a.m. |
Created at: April 21, 2026, 12:16 p.m.