Triple
T24779759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nevern estuary |
E619959
|
entity |
| Predicate | drainsCatchment |
P1559
|
FINISHED |
| Object | River Nevern 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 Nevern catchment | Statement: [Nevern estuary, drainsCatchment, River Nevern catchment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drainsCatchment Context triple: [Nevern estuary, drainsCatchment, River Nevern catchment]
-
A.
drainageBasin
chosen
Indicates the area of land where all precipitation and surface water flow are collected and drained toward a particular river, lake, or other water body.
-
B.
reservoirCatchment
Indicates that one entity is the catchment area that drains water into a specified reservoir.
-
C.
drainsInto
Indicates that one entity serves as a source or conduit whose contents or flow are directed into another entity.
-
D.
drainageDivideOf
Indicates that one geographic feature functions as the drainage divide (separating water flow into different basins) for another feature or area.
-
E.
hasBodyOfWaterDrainedBy
Indicates that a body of water is emptied or its water flow is carried away by a specified draining feature, such as a river, channel, or drainage system.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:43 a.m.