Triple
T15048170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2002 European floods |
E379285
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | disaster in Europe |
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 Europe Context triple: [2002 European floods, instanceOf, disaster in Europe]
-
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.
European war
A European war is a large-scale armed conflict primarily involving multiple nation-states within Europe, often driven by territorial, political, or ideological disputes that significantly reshape the continent’s balance of power.
-
C.
region of Europe
A region of Europe is a geographically or culturally defined area within the European continent that shares common physical, historical, political, or socio-economic characteristics distinguishing it from other areas.
-
D.
Balkan crisis
The Balkan crisis refers to a series of political, ethnic, and territorial conflicts in the Balkan region—especially in the late 19th, early 20th, and late 20th centuries—that destabilized Europe and contributed to major international confrontations, including World War I and the Yugoslav Wars.
-
E.
eurodistrict
A eurodistrict is a cross-border administrative and cooperation entity formed by neighboring local authorities from different European countries to coordinate services, planning, and development in a shared transnational region.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3 a.m.