Triple
T27649000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kidsty Pike |
E696794
|
entity |
| Predicate | partOfWatershedBetween |
P121776
|
FINISHED |
| Object | Eden catchment |
—
|
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: Eden catchment | Statement: [Kidsty Pike, partOfWatershedBetween, Eden catchment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfWatershedBetween Context triple: [Kidsty Pike, partOfWatershedBetween, Eden catchment]
-
A.
watershedBetween
Indicates that a geographic feature or boundary serves as the dividing line between two drainage basins or river systems.
-
B.
liesOnWatershedBetween
chosen
Indicates that something is located on or along the dividing line between two drainage basins or watersheds.
-
C.
isHeadwaterTributaryOf
Indicates that one watercourse is a source or upstream tributary that feeds into another watercourse.
-
D.
isSharedWatercourseBetween
Indicates that a watercourse (such as a river, stream, or canal) is jointly used, bordered, or managed by two or more distinct entities (e.g., regions, countries, or properties).
-
E.
drainageBasinOnOtherSide
Indicates that the drainage basin associated with one entity lies on the opposite side of a dividing feature (such as a watershed or boundary) from the drainage basin associated with another entity.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: April 27, 2026, 2:31 p.m.