Triple
T10299084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coralville Dam |
E241576
|
entity |
| Predicate | effectOf2008Flood |
P50010
|
FINISHED |
| Object | further erosion and exposure of Devonian Fossil Gorge |
—
|
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: further erosion and exposure of Devonian Fossil Gorge | Statement: [Coralville Dam, effectOf2008Flood, further erosion and exposure of Devonian Fossil Gorge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOf2008Flood Context triple: [Coralville Dam, effectOf2008Flood, further erosion and exposure of Devonian Fossil Gorge]
-
A.
floodConsequence
chosen
Indicates the resulting effects, outcomes, or impacts that occur as a consequence of a flood event.
-
B.
floodEvent
Indicates an occurrence of a flooding event affecting a location, time period, or set of impacted entities.
-
C.
floodCause
Indicates that one entity is the cause or source of a flood affecting another entity or area.
-
D.
notableFloodEvents
Indicates that there are significant or historically important flood occurrences associated with the given entity.
-
E.
floodEventMotivation
Indicates the underlying reason, cause, or driving factor that led to the occurrence of a specific flood event.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2ee10f88190b1615c49b8f24a26 |
completed | April 7, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f35e548190be3b4d92d65d2d20 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:44 a.m.