Triple
T29566326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shepperton Weir |
E753171
|
entity |
| Predicate | downstreamReach |
P110130
|
FINISHED |
| Object | reach between Shepperton Lock and Chertsey Lock |
—
|
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: reach between Shepperton Lock and Chertsey Lock | Statement: [Shepperton Weir, downstreamReach, reach between Shepperton Lock and Chertsey Lock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: downstreamReach Context triple: [Shepperton Weir, downstreamReach, reach between Shepperton Lock and Chertsey Lock]
-
A.
downstreamFrom
Indicates that one entity is located or occurs at a point further along the natural flow or direction of another entity, typically in a linear or directional system such as a river, pipeline, or process sequence.
-
B.
downstreamBoundary
Indicates that one entity serves as the downstream limit or endpoint of another entity’s flow, process, or influence.
-
C.
downstreamReservoir
Indicates that one reservoir is located downstream of, and receives water flow from, another reservoir in a connected water system.
-
D.
downstreamUse
Indicates that one entity makes use of the outputs, results, or products generated by another entity at a later stage in a process or workflow.
-
E.
downstreamRiverSection
chosen
Indicates that one river section is located downstream from, and receives flow from, another river section.
- 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_69f0ef7fcb4881908a933110adb9bda1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66d4323708190a12d588bf6a512b3 |
completed | May 2, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 5:52 p.m.