Triple
T2626482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Dwyryd |
E59128
|
entity |
| Predicate | hasEstuarineEnvironment |
P28855
|
FINISHED |
| Object | tidal estuary near Porthmadog |
—
|
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: tidal estuary near Porthmadog | Statement: [River Dwyryd, hasEstuarineEnvironment, tidal estuary near Porthmadog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEstuarineEnvironment Context triple: [River Dwyryd, hasEstuarineEnvironment, tidal estuary near Porthmadog]
-
A.
hasEstuaryType
Indicates the specific type or classification of an estuary associated with a given water body or location.
-
B.
hasEstuaryNear
chosen
Indicates that the estuary of a water body is located in close proximity to a specified place or feature.
-
C.
hasCoastalEnvironment
Indicates that an entity is located in, adjacent to, or characterized by a coastal environment or shoreline setting.
-
D.
hasMarineEcosystem
Indicates that an entity possesses, contains, or is associated with a marine ecosystem as part of its characteristics or environment.
-
E.
hasMarineEcoregion
Indicates that an entity is associated with, or located within, a specific marine ecoregion.
- 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_69ab4ac558388190962492cd2e1b0ce6 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abdb0e7b888190bfa5d2e33f00ec0f |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd810d7f481908e81c305772c4c14 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.