Triple
T24068203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sleights road bridge |
E596151
|
entity |
| Predicate | hasWatercourseBelow |
P139261
|
FINISHED |
| Object | River Esk, North Yorkshire |
—
|
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 Esk, North Yorkshire | Statement: [Sleights road bridge, hasWatercourseBelow, River Esk, North Yorkshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWatercourseBelow Context triple: [Sleights road bridge, hasWatercourseBelow, River Esk, North Yorkshire]
-
A.
hasRiverBelow
chosen
Indicates that one entity is located above another such that a river lies physically below it.
-
B.
watercourseBelow
Indicates that one watercourse lies downstream or at a lower elevation relative to another watercourse.
-
C.
hasWatercourseType
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
-
D.
hasPositionInWatercourse
Indicates that one entity occupies a specific location or position within the course of a body of water.
-
E.
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.
- 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_69e288c25c008190850cf447940ab181 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1da5c57e88190ba05cc41b8fd035a |
completed | April 29, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:40 p.m.