Triple
T9440153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kakhovka Reservoir |
E227621
|
entity |
| Predicate | dateOfMajorDrainageEvent |
P88904
|
FINISHED |
| Object | June 2023 |
—
|
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: June 2023 | Statement: [Kakhovka Reservoir, dateOfMajorDrainageEvent, June 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfMajorDrainageEvent Context triple: [Kakhovka Reservoir, dateOfMajorDrainageEvent, June 2023]
-
A.
notableFloodEvents
Indicates that there are significant or historically important flood occurrences associated with the given entity.
-
B.
floodEvent
Indicates an occurrence of a flooding event affecting a location, time period, or set of impacted entities.
-
C.
floodRecord
Indicates that an entity serves as a documented record or report of a flood event affecting another entity or area.
-
D.
runoffDate
Indicates the date on which a runoff event (such as a runoff election or runoff water occurrence) takes place or is scheduled.
-
E.
eraOfMajorDrainageWorks
Indicates the time period during which significant drainage or water-management construction activities took place.
- F. None of above. chosen
Provenance (4 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_69ca843884488190ad6cbe0153088234 |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7ee36f908190826994db91b18466 |
completed | April 1, 2026, 8:24 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:50 p.m.