Triple
T34409442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ouse Washes |
E883213
|
entity |
| Predicate | betweenWatercourses |
P90513
|
FINISHED |
| Object | River Great Ouse |
—
|
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 Great Ouse | Statement: [Ouse Washes, betweenWatercourses, River Great Ouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: betweenWatercourses Context triple: [Ouse Washes, betweenWatercourses, River Great Ouse]
-
A.
watershedBetween
Indicates that a geographic feature or boundary serves as the dividing line between two drainage basins or river systems.
-
B.
watercourseSupports
Indicates that a watercourse provides the necessary conditions or resources to sustain another entity, process, or activity.
-
C.
isWatercourseOf
Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
-
D.
betweenRiver
chosen
Indicates a spatial relationship where something is located in the area separating two rivers or lies in the intermediate region defined by them.
-
E.
inflowWatercourse
Indicates that one watercourse flows into or feeds another water body or watercourse.
- 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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.