Triple
T12082805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleethorpes |
E287722
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | CLEETHORPES |
E789474
|
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: CLEETHORPES | Statement: [Cleethorpes, hasPostTown, CLEETHORPES]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CLEETHORPES Context triple: [Cleethorpes, hasPostTown, CLEETHORPES]
-
A.
CLEETHORPES
chosen
CLEETHORPES is a seaside resort and town on the east coast of England, known for its sandy beaches and traditional promenade.
-
B.
Thorpe Ward
Thorpe Ward is a local electoral division that represents the Thorpe Bay area within its governing council.
-
C.
Epping
Epping is a suburb in Melbourne, Australia, known for its residential communities, shopping facilities, and role as a transport hub in the city's northern corridor.
-
D.
Epping
Epping is a market town in the Epping Forest district of Essex, England, known for its historic high street and proximity to the ancient Epping Forest.
-
E.
Cheshunt
Cheshunt is a town in Hertfordshire, England, situated just north of London and known as a commuter hub with rail links into the capital.
- 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915124e4c8190b0264c2a09e3c2f3 |
completed | April 10, 2026, 3:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f66509208190b7206e78df41c2fe |
completed | May 2, 2026, 1:04 p.m. |
Created at: April 8, 2026, 9:48 p.m.