Triple
T29611115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Yeo (Barnstaple) |
E754722
|
entity |
| Predicate | hasEstuarineConnection |
P137069
|
FINISHED |
| Object | Taw–Torridge estuary system |
—
|
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: Taw–Torridge estuary system | Statement: [River Yeo (Barnstaple), hasEstuarineConnection, Taw–Torridge estuary system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEstuarineConnection Context triple: [River Yeo (Barnstaple), hasEstuarineConnection, Taw–Torridge estuary system]
-
A.
hasEstuaryWith
chosen
Indicates that a river or watercourse flows into and forms an estuary with a particular body of water.
-
B.
hasEstuaryAt
Indicates that a river or watercourse flows into and meets a larger body of water (such as a sea, ocean, or lake) at a specific location.
-
C.
isEstuarine
Indicates that something is located in, formed in, or characteristic of an estuary, where river and seawater environments meet.
-
D.
hasEstuaryNear
Indicates that the estuary of a water body is located in close proximity to a specified place or feature.
-
E.
hasEstuaryType
Indicates the specific type or classification of an estuary associated with a given water body or location.
- 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66deaf7ac8190b0be57d7f18d0c9b |
completed | May 2, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:28 p.m.