Triple
T17690538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rochford |
E441013
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Southend-on-Sea |
—
|
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: Southend-on-Sea | Statement: [Rochford, locatedNear, Southend-on-Sea]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Southend-on-Sea Context triple: [Rochford, locatedNear, Southend-on-Sea]
-
A.
Southend-on-Sea
chosen
Southend-on-Sea is a coastal resort city in Essex, England, known for its seaside tourism and the world’s longest pleasure pier.
-
B.
Southend
Southend is a small locality in Buckinghamshire, England, known primarily as a rural village within the county.
-
C.
Southend
Southend is a small coastal village located at the southern tip of the Kintyre peninsula in Argyll and Bute, Scotland.
-
D.
Southend
Southend is a small coastal town in South Australia known for its beaches, fishing, and proximity to protected natural areas.
-
E.
Leigh-on-Sea
Leigh-on-Sea is a coastal town in Essex, England, known for its historic fishing village, estuary views, and vibrant arts and café culture.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4704b43a88190ba29654ca695839e |
completed | April 19, 2026, 6:03 a.m. |
Created at: April 10, 2026, 10:03 a.m.