Triple
T26423232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foss Barrier and pumping station |
E664297
|
entity |
| Predicate | managesWatercourse |
P68423
|
FINISHED |
| Object | River Foss |
—
|
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: River Foss | Statement: [Foss Barrier and pumping station, managesWatercourse, River Foss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesWatercourse Context triple: [Foss Barrier and pumping station, managesWatercourse, River Foss]
-
A.
watercourseControlled
chosen
Indicates that one entity exercises control, regulation, or management over a watercourse (such as a river, stream, or canal).
-
B.
inflowWatercourse
Indicates that one watercourse flows into or feeds another water body or watercourse.
-
C.
managesWaterFrom
Indicates that one entity is responsible for controlling, directing, or handling water originating from another entity.
-
D.
riverManaged
Indicates that a river is subject to management, regulation, or oversight by a particular authority, organization, or system.
-
E.
riverRegulation
Indicates the management or control of a river’s flow, level, or course through human interventions such as dams, channels, or other regulatory measures.
- 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_69ee883a04ec81908883c4559f8c7e24 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 26, 2026, 11:44 p.m.