Triple
T6714140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheringham |
E153220
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | SHERINGHAM |
E153220
|
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: SHERINGHAM | Statement: [Sheringham, hasPostTown, SHERINGHAM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SHERINGHAM Context triple: [Sheringham, hasPostTown, SHERINGHAM]
-
A.
Norwich to Sheringham
Norwich to Sheringham is a regional rail passenger service in Norfolk, England, linking the city of Norwich with the coastal town of Sheringham.
-
B.
Hunstanton
Hunstanton is a seaside town on the north coast of Norfolk, England, known for its distinctive striped cliffs and sandy beaches on The Wash.
-
C.
Aylsham
Aylsham is a historic market town in eastern England known for its traditional architecture and proximity to the Norfolk Broads.
-
D.
Sheringham
chosen
Sheringham is a seaside town and popular tourist resort on the north coast of Norfolk, England, known for its beaches, heritage railway, and access to coastal walking paths.
-
E.
Seaham
Seaham is a small rural town in the Hunter Region of New South Wales, Australia, known for its historic buildings and riverside setting.
- 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_69c68809b4608190a2509ddb5ab87f05 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d122d6cc81909bde0c94fb95f016 |
completed | March 27, 2026, 6:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c70096e05c8190abfa90996db37eeb |
completed | March 27, 2026, 10:11 p.m. |
Created at: March 27, 2026, 2:07 p.m.