Triple
T5076252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breich Water |
E114403
|
entity |
| Predicate | hasWatershedRegion |
P17416
|
FINISHED |
| Object | River Almond 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: River Almond catchment | Statement: [Breich Water, hasWatershedRegion, River Almond catchment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWatershedRegion Context triple: [Breich Water, hasWatershedRegion, River Almond catchment]
-
A.
hasWatershed
chosen
Indicates that one geographic area or feature is part of, drains into, or is hydrologically defined by a particular watershed.
-
B.
hasWatershedWith
Indicates that two geographic areas share or are associated with the same watershed or drainage basin.
-
C.
hasWatershedCharacteristic
Indicates that a watershed possesses a specified characteristic, feature, or property.
-
D.
hasWatershedUse
Indicates that a particular type of use, activity, or function is associated with or applied to a watershed.
-
E.
watershedBetween
Indicates that a geographic feature or boundary serves as the dividing line between two drainage basins or river systems.
- 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_69bd443dbf908190a9401e9c2dc7bd7d |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74d3b0088190a658864cb120eef4 |
completed | March 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.