Triple
T28754246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saylorville Dam |
E731621
|
entity |
| Predicate | controlsFloodingFor |
P42410
|
FINISHED |
| Object | Des Moines metropolitan area |
—
|
NE NERFINISHED |
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: Des Moines metropolitan area | Statement: [Saylorville Dam, controlsFloodingFor, Des Moines metropolitan area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlsFloodingFor Context triple: [Saylorville Dam, controlsFloodingFor, Des Moines metropolitan area]
-
A.
providesFloodControlFor
chosen
Indicates that one entity offers protection or mitigation against flooding for another entity or area.
-
B.
reasonForFlooding
Indicates the cause or underlying factor that led to the occurrence of flooding.
-
C.
isFlooded
Indicates that a location, area, or object is currently covered or overwhelmed by an abnormal amount of water.
-
D.
hasFloodControlStructure
Indicates that an entity possesses or is equipped with a structure designed to manage, control, or mitigate flooding.
-
E.
hasFloodProtectionProject
Indicates that a flood protection project exists or is implemented for the referenced entity.
- 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 28, 2026, 6:09 a.m.