Triple
T3472573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walcheren |
E73296
|
entity |
| Predicate | wasFloodedIn |
P17084
|
FINISHED |
| Object | 1944 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 1944 | Statement: [Walcheren, wasFloodedIn, 1944]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFloodedIn Context triple: [Walcheren, wasFloodedIn, 1944]
-
A.
hasFloodHistory
chosen
Indicates that the subject has experienced one or more flood events in the past.
-
B.
hasFloodRisk
Indicates that an entity is exposed to a potential or expected risk of flooding under certain conditions.
-
C.
wasIn
Indicates that an entity existed, occurred, or was located within a particular place or context during a specified time or situation.
-
D.
floodEvent
Indicates an occurrence of a flooding event affecting a location, time period, or set of impacted entities.
-
E.
wasBombardedDuring
Indicates that an entity was subjected to a bombardment (e.g., shelling, bombing, or heavy attack) during a specified event or time period.
- F. None of above.
Provenance (3 batches)
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_69ad85b2fed48190948c8765e453d270 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb3cc8488190b97c732e3f600a90 |
completed | March 8, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69adae07802c8190919c49b0e65b2797 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.