Triple
T13890372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandown Pier |
E333953
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Sandown beach |
E333954
|
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: Sandown beach | Statement: [Sandown Pier, near, Sandown beach]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sandown beach Context triple: [Sandown Pier, near, Sandown beach]
-
A.
Sandown Beach
chosen
Sandown Beach is a popular sandy seaside destination on the Isle of Wight in England, known for its long promenade, family-friendly atmosphere, and traditional resort-town amenities.
-
B.
Aberavon Beach
Aberavon Beach is a long sandy seaside resort in Port Talbot, South Wales, popular for walking, surfing, and coastal recreation along Swansea Bay.
-
C.
Swansea Beach
Swansea Beach is a long sandy shoreline in Swansea, Wales, popular for seaside recreation and coastal views across Swansea Bay.
-
D.
Hythe beach
Hythe beach is a shingle shoreline on the south coast of Kent, England, known for its long promenade, coastal views, and traditional seaside atmosphere.
-
E.
Selsey Beach
Selsey Beach is a popular shingle and sand beach on England’s south coast, known for its seaside promenade, fishing heritage, and views across the English Channel.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a3a24881908d81d634622fbbcc |
completed | April 14, 2026, 11:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd192b5e508190b2d385657f9e358f |
completed | May 7, 2026, 10:58 p.m. |
Created at: April 9, 2026, 10:15 p.m.