Triple
T15635064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1957 Valencia flood |
E375919
|
entity |
| Predicate | floodPeakDischarge |
P119545
|
FINISHED |
| Object | over 3000 m3/s |
—
|
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: over 3000 m3/s | Statement: [1957 Valencia flood, floodPeakDischarge, over 3000 m3/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floodPeakDischarge Context triple: [1957 Valencia flood, floodPeakDischarge, over 3000 m3/s]
-
A.
designedFloodDischarge
Indicates the planned or specified amount of water flow that a structure or system is engineered to safely discharge during flood conditions.
-
B.
floodPeakLocation
Indicates the location at which the maximum intensity or highest level of a flood event occurs.
-
C.
floodGauge
Indicates that a device or measurement point is used to monitor and record the level or intensity of flooding at a specific location.
-
D.
floodRecord
Indicates that an entity serves as a documented record or report of a flood event affecting another entity or area.
-
E.
floodEvent
Indicates an occurrence of a flooding event affecting a location, time period, or set of impacted entities.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eb8b4c48190b80fea6877483089 |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:14 a.m.