Triple
T24403734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Eden (Fife) |
E615248
|
entity |
| Predicate | estuaryProtectedAs |
P156063
|
FINISHED |
| Object | Local Nature Reserve |
—
|
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: Local Nature Reserve | Statement: [River Eden (Fife), estuaryProtectedAs, Local Nature Reserve]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estuaryProtectedAs Context triple: [River Eden (Fife), estuaryProtectedAs, Local Nature Reserve]
-
A.
estuaryDesignation
Indicates that a body of water or coastal area has been formally identified or classified as an estuary.
-
B.
estuaryStatus
Indicates the condition or classification of an estuary, such as its current state, health, or regulatory status.
-
C.
isEstuarine
Indicates that something is located in, formed in, or characteristic of an estuary, where river and seawater environments meet.
-
D.
estuaryName
Indicates the naming relationship that assigns a specific name to an estuary.
-
E.
hasEstuaryWith
Indicates that a river or watercourse flows into and forms an estuary with a particular body of water.
- F. None of above. chosen
Provenance (4 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_69e2d7e780bc81908049c779e697a7f6 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f294dcf7f4819094d2a3be163a5822 |
completed | April 29, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:05 a.m.