Triple
T27648880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Storm Desmond |
E696790
|
entity |
| Predicate | associatedRiverFlooding |
P34423
|
FINISHED |
| Object | River Eden |
—
|
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: River Eden | Statement: [Storm Desmond, associatedRiverFlooding, River Eden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRiverFlooding Context triple: [Storm Desmond, associatedRiverFlooding, River Eden]
-
A.
floodEvent
Indicates an occurrence of a flooding event affecting a location, time period, or set of impacted entities.
-
B.
floodCause
chosen
Indicates that one entity is the cause or source of a flood affecting another entity or area.
-
C.
floodLocation
Indicates that a flooding event occurs at, affects, or is situated in a specified location.
-
D.
hasFloodRisk
Indicates that an entity is exposed to a potential or expected risk of flooding under certain conditions.
-
E.
floodSeasonCause
Indicates the cause or contributing factor responsible for a particular flood season occurring.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_6a00372ff0e48190b3ed91f9bae9da6c |
completed | May 10, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_6a00359c1b8481909c1e43df9f5a789a |
completed | May 10, 2026, 7:37 a.m. |
Created at: April 27, 2026, 2:31 p.m.