Triple
T32322009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duddon Sands |
E825797
|
entity |
| Predicate | bayOrEstuary |
P47386
|
FINISHED |
| Object | Duddon Estuary |
—
|
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: Duddon Estuary | Statement: [Duddon Sands, bayOrEstuary, Duddon Estuary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bayOrEstuary Context triple: [Duddon Sands, bayOrEstuary, Duddon Estuary]
-
A.
bayOf
chosen
Indicates that one location is a bay that forms an inlet or coastal indentation associated with another geographic entity, such as a sea, ocean, or coastline.
-
B.
estuaryName
Indicates the naming relationship that assigns a specific name to an estuary.
-
C.
isEstuarine
Indicates that something is located in, formed in, or characteristic of an estuary, where river and seawater environments meet.
-
D.
bay
Indicates that one entity howls or barks loudly, often repeatedly, typically in reaction to something such as prey, the moon, or a disturbance.
-
E.
hasEstuaryNear
Indicates that the estuary of a water body is located in close proximity to a specified place or feature.
- 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_69f34912d0c48190bba75770660320e9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bde419a48190b76643481d078c4e |
completed | May 3, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:47 a.m.