Triple
T23490727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yolo Bypass |
E570664
|
entity |
| Predicate | managesFloodwatersFrom |
P21624
|
FINISHED |
| Object | Sacramento River |
—
|
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: Sacramento River | Statement: [Yolo Bypass, managesFloodwatersFrom, Sacramento River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesFloodwatersFrom Context triple: [Yolo Bypass, managesFloodwatersFrom, Sacramento River]
-
A.
managesFloodRisk
Indicates a relationship where one entity takes actions or implements measures to control, reduce, or mitigate the risk and impact of flooding on another entity or area.
-
B.
managesWaterFrom
chosen
Indicates that one entity is responsible for controlling, directing, or handling water originating from another entity.
-
C.
floodEvent
Indicates an occurrence of a flooding event affecting a location, time period, or set of impacted entities.
-
D.
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.
-
E.
riverManaged
Indicates that a river is subject to management, regulation, or oversight by a particular authority, organization, or system.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7dba7388190a322ab059bb6522a |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:04 p.m.