Triple
T25545122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Room for the River programme |
E640276
|
entity |
| Predicate | maximumDesignDischarge |
P50049
|
FINISHED |
| Object | 16000 m3/s at Lobith |
—
|
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: 16000 m3/s at Lobith | Statement: [Room for the River programme, maximumDesignDischarge, 16000 m3/s at Lobith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumDesignDischarge Context triple: [Room for the River programme, maximumDesignDischarge, 16000 m3/s at Lobith]
-
A.
designedFloodDischarge
chosen
Indicates the planned or specified amount of water flow that a structure or system is engineered to safely discharge during flood conditions.
-
B.
maximumDischarge
Indicates the greatest allowable or observed rate at which something can be discharged or released from a source.
-
C.
designedFloodLevel
Indicates the flood level that a structure or system is specifically engineered to withstand or accommodate.
-
D.
floodPeakDischarge
Indicates the maximum rate of water flow occurring at the peak of a flood event in a river or channel.
-
E.
maximumWaterDepth
Indicates the greatest depth of water present or allowed in a given context, such as a location, container, or body of water.
- 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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 21, 2026, 3:28 p.m.