Triple
T26314836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ecclesbourne Valley |
E661939
|
entity |
| Predicate | watercourseSourceRegion |
P72158
|
FINISHED |
| Object | southern Pennine foothills |
—
|
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: southern Pennine foothills | Statement: [Ecclesbourne Valley, watercourseSourceRegion, southern Pennine foothills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: watercourseSourceRegion Context triple: [Ecclesbourne Valley, watercourseSourceRegion, southern Pennine foothills]
-
A.
waterSourceRegion
chosen
Indicates that a specified region serves as the geographic source or origin area of a particular body or supply of water.
-
B.
watercourseThroughRegion
Indicates that a watercourse (such as a river or stream) passes through or traverses a specified region.
-
C.
sourceOfWatercourse
Indicates that one entity is the origin or starting point from which a watercourse (such as a river or stream) begins or flows.
-
D.
majorRiverSource
Indicates that one entity is the primary originating source or headwaters location of a major river.
-
E.
hasHeadwatersOf
Indicates that a specified location or feature is the source or origin point of a particular river 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 26, 2026, 10:24 p.m.