Triple
T34409450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ouse Washes |
E883213
|
entity |
| Predicate | managesFloodwaterFrom |
P21624
|
FINISHED |
| Object | River Great Ouse |
—
|
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 Great Ouse | Statement: [Ouse Washes, managesFloodwaterFrom, River Great Ouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesFloodwaterFrom Context triple: [Ouse Washes, managesFloodwaterFrom, River Great Ouse]
-
A.
managesFloodRisk
Indicates a relationship where one entity takes actions or implements measures to control, reduce, or mitigate the risk and impact of flooding on another entity or area.
-
B.
designedForFloodMitigationOf
Indicates that something is specifically created or configured to reduce, control, or manage flooding affecting a particular entity or area.
-
C.
managesWaterFrom
chosen
Indicates that one entity is responsible for controlling, directing, or handling water originating from another entity.
-
D.
floodEvent
Indicates an occurrence of a flooding event affecting a location, time period, or set of impacted entities.
-
E.
floodEnhancedBy
Indicates that the occurrence, intensity, or impact of a flood is increased or made more severe by the associated factor or condition.
- 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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 1, 2026, 1:59 a.m.