Triple
T35005209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boscastle |
E1009789
|
entity |
| Predicate | floodEventResponse |
P182800
|
FINISHED |
| Object | major rescue operation by emergency services |
—
|
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: major rescue operation by emergency services | Statement: [Boscastle, floodEventResponse, major rescue operation by emergency services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floodEventResponse Context triple: [Boscastle, floodEventResponse, major rescue operation by emergency services]
-
A.
floodEvent
Indicates an occurrence of a flooding event affecting a location, time period, or set of impacted entities.
-
B.
floodEventsCount
Indicates the number of flood events that have occurred or been recorded for a given context or entity.
-
C.
floodEventMotivation
Indicates the underlying reason, cause, or driving factor that led to the occurrence of a specific flood event.
-
D.
floodRecord
Indicates that an entity serves as a documented record or report of a flood event affecting another entity or area.
-
E.
notableFloodEvents
Indicates that there are significant or historically important flood occurrences associated with the given entity.
- 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_69f7908ec35881909a42f954fb9fa16e |
completed | May 3, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78fd3fd888190b7db0b563f298585 |
completed | May 3, 2026, 6:11 p.m. |
Created at: May 3, 2026, 4:01 p.m.