Triple
T29611230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Braunton Burrows |
E754727
|
entity |
| Predicate | locatedAtEstuaryOf |
P117224
|
FINISHED |
| Object | River Taw |
—
|
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: River Taw | Statement: [Braunton Burrows, locatedAtEstuaryOf, River Taw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedAtEstuaryOf Context triple: [Braunton Burrows, locatedAtEstuaryOf, River Taw]
-
A.
locatedInEstuarySystem
chosen
Indicates that something is situated within or forms part of an estuary system, where riverine and marine environments interact.
-
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.
estuaryLocatedIn
Indicates that an estuary is geographically situated within or along the boundaries of a specified larger region or area.
-
D.
locatedOnTributaryOf
Indicates that one entity is situated along or on the banks of a tributary that flows into another specified water body.
-
E.
hasCityOnEstuary
Indicates that a city is located on or adjacent to the estuary of a river.
- 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a0048697bd081909073640666ca6a96 |
completed | May 10, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_6a0047bf3c248190a9ac97a7afdfe2cb |
completed | May 10, 2026, 8:54 a.m. |
Created at: April 28, 2026, 6:28 p.m.