Triple
T14136390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Lynher |
E350305
|
entity |
| Predicate | hasEstuarineSection |
P109738
|
FINISHED |
| Object | upper Tamar estuary |
—
|
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: upper Tamar estuary | Statement: [River Lynher, hasEstuarineSection, upper Tamar estuary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEstuarineSection Context triple: [River Lynher, hasEstuarineSection, upper Tamar estuary]
-
A.
hasEstuarySection
chosen
Indicates that a watercourse includes a section where it widens and meets a larger body of water, forming an estuary.
-
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.
hasEstuaryType
Indicates the specific type or classification of an estuary associated with a given water body or location.
-
D.
hasEstuaryNear
Indicates that the estuary of a water body is located in close proximity to a specified place or feature.
-
E.
hasFreshwaterSection
Indicates that an entity includes or contains a distinct section or area composed of freshwater.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de610fb86c81909eb26bf9c13696ca |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:18 a.m.