Triple
T29111525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zwenkauer See |
E736919
|
entity |
| Predicate | floodingCompletion |
P106727
|
FINISHED |
| Object | around 2014 |
—
|
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: around 2014 | Statement: [Zwenkauer See, floodingCompletion, around 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floodingCompletion Context triple: [Zwenkauer See, floodingCompletion, around 2014]
-
A.
floodedFor
Indicates that one entity is intentionally inundated or submerged with water (or another liquid) for the benefit, use, or purpose of another entity.
-
B.
drainageCompletedIn
Indicates that the process of draining (e.g., water or fluid removal) was fully completed within a specified time, place, or context.
-
C.
submergenceCompleted
chosen
Indicates that the process of submerging an entity in a medium (such as liquid or water) has been fully completed.
-
D.
formedByFlooding
Indicates that something came into existence or was created as a result of flooding.
-
E.
floodEvent
Indicates an occurrence of a flooding event affecting a location, time period, or set of impacted entities.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f661be0108819090cae6a19ae4157d |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 11:19 a.m.