Triple
T13698381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hythe beach |
E328447
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Dymchurch |
E321017
|
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: Dymchurch | Statement: [Hythe beach, near, Dymchurch]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dymchurch Context triple: [Hythe beach, near, Dymchurch]
-
A.
Dymchurch
chosen
Dymchurch is a coastal village on the southeast coast of England, known for its sandy beach, sea wall, and role in the Romney Marsh area of Kent.
-
B.
Neatishead
Neatishead is a small village in Norfolk, England, situated within the Norfolk Broads national park and known for its riverside setting and traditional rural character.
-
C.
Hornsea
Hornsea is a small seaside town and former fishing village on the North Sea coast of the East Riding of Yorkshire in England, known for its beach, promenade, and nearby Hornsea Mere.
-
D.
Weybourne
Weybourne is a coastal village in Norfolk, England, known for its shingle beach, scenic cliffs, and proximity to the North Norfolk heritage railway.
-
E.
Weybourne
Weybourne is a residential area and village in Surrey, England, situated on the outskirts of the town of Farnham.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc878b57c819094e7ea6d1a64211f |
completed | April 12, 2026, 4:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f794559e9c81909ef8a6d9b9f480b3 |
completed | May 3, 2026, 6:30 p.m. |
Created at: April 9, 2026, 9:54 p.m.