Triple
T35005210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boscastle |
E1009789
|
entity |
| Predicate | postFloodMeasure |
P181983
|
FINISHED |
| Object | flood defence improvements |
—
|
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: flood defence improvements | Statement: [Boscastle, postFloodMeasure, flood defence improvements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postFloodMeasure Context triple: [Boscastle, postFloodMeasure, flood defence improvements]
-
A.
floodEvent
Indicates an occurrence of a flooding event affecting a location, time period, or set of impacted entities.
-
B.
floodGauge
Indicates that a device or measurement point is used to monitor and record the level or intensity of flooding at a specific location.
-
C.
floodRecord
Indicates that an entity serves as a documented record or report of a flood event affecting another entity or area.
-
D.
floodEnhancedBy
Indicates that the occurrence, intensity, or impact of a flood is increased or made more severe by the associated factor or condition.
-
E.
floodStage
Indicates that a water body’s level has reached or exceeded the defined height at which flooding is expected to begin or become hazardous.
- F. None of above. chosen
Provenance (4 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_69f76dcb716881909f75e4fd60ab2284 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7865578d48190bf90e470634fd97d |
completed | May 3, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f78575917481909a3defd6a4c366bd |
completed | May 3, 2026, 5:27 p.m. |
Created at: May 3, 2026, 4:01 p.m.