Triple
T25663011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Wansbeck |
E643435
|
entity |
| Predicate | hasFloodHistoryIn |
P17084
|
FINISHED |
| Object | Morpeth |
—
|
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: Morpeth | Statement: [River Wansbeck, hasFloodHistoryIn, Morpeth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFloodHistoryIn Context triple: [River Wansbeck, hasFloodHistoryIn, Morpeth]
-
A.
hasFloodHistory
chosen
Indicates that the subject has experienced one or more flood events in the past.
-
B.
hasFloodRisk
Indicates that an entity is exposed to a potential or expected risk of flooding under certain conditions.
-
C.
floodRecord
Indicates that an entity serves as a documented record or report of a flood event affecting another entity or area.
-
D.
hasFloodProtectionProject
Indicates that a flood protection project exists or is implemented for the referenced entity.
-
E.
hasFloodRiskAreas
Indicates that certain areas are subject to potential flooding or are classified as being at risk of flood events.
- 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_69e77e7e45648190a068ed3faa8016ea |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5faf125388190bf20dd812f1a2632 |
completed | May 2, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 6:57 p.m.