Triple
T13277801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kelling Heath |
E316237
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Weybourne |
E613221
|
NE 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: Weybourne | Statement: [Kelling Heath, locatedNear, Weybourne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Weybourne Context triple: [Kelling Heath, locatedNear, Weybourne]
-
A.
Weybourne
Weybourne is a residential area and village in Surrey, England, situated on the outskirts of the town of Farnham.
-
B.
Weybourne
chosen
Weybourne is a coastal village in Norfolk, England, known for its shingle beach, scenic cliffs, and proximity to the North Norfolk heritage railway.
-
C.
Burnham-on-Sea
Burnham-on-Sea is a small seaside resort town on the Bristol Channel coast of Somerset in southwest England, known for its sandy beaches and historic low lighthouse.
-
D.
Thrupp
Thrupp is a small canal-side village in Oxfordshire, England, known for its historic wharf and picturesque setting along the Oxford Canal.
-
E.
Tenterden
Tenterden is a historic market town in Kent, England, known for its traditional high street, heritage railway, and surrounding Wealden countryside.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99043fba88190872ede6f63e2fbcb |
completed | April 11, 2026, 12:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f70a54ff488190a759b46963c0d842 |
completed | May 3, 2026, 8:41 a.m. |
Created at: April 9, 2026, 9:26 p.m.