Triple
T27480681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wyre catchment |
E693590
|
entity |
| Predicate | drainsTributary |
P4497
|
FINISHED |
| Object | River Brock |
—
|
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 Brock | Statement: [Wyre catchment, drainsTributary, River Brock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drainsTributary Context triple: [Wyre catchment, drainsTributary, River Brock]
-
A.
tributary
Indicates that one watercourse flows into and feeds another, contributing its water to a larger stream, river, or lake.
-
B.
drainsInto
chosen
Indicates that one entity serves as a source or conduit whose contents or flow are directed into another entity.
-
C.
isHeadwaterTributaryOf
Indicates that one watercourse is a source or upstream tributary that feeds into another watercourse.
-
D.
tributarySystem
Indicates a relationship where one political entity pays regular tribute or offers deference to another, acknowledging the latter’s superior authority or status.
-
E.
isTributaryDamOf
Indicates that a dam is constructed on and regulates the flow of a tributary river or stream relative to a main 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_69ef5381f2648190a2392d0fab833095 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 12:59 p.m.