Triple
T9811665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kent Downs |
E238286
|
entity |
| Predicate | nearbyTown |
P3883
|
FINISHED |
| Object | Folkestone |
E213999
|
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: Folkestone | Statement: [Kent Downs, nearbyTown, Folkestone]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Folkestone Context triple: [Kent Downs, nearbyTown, Folkestone]
-
A.
Folkestone
chosen
Folkestone is a coastal town and port in Kent, England, known as a gateway to continental Europe via the Channel Tunnel and nearby ferry links.
-
B.
Folkestone and Hythe
Folkestone and Hythe is a UK parliamentary constituency in Kent that covers the coastal towns of Folkestone and Hythe and their surrounding areas.
-
C.
Ramsgate
Ramsgate is a seaside town and port on the Isle of Thanet in Kent, England, known historically as a popular resort and maritime hub.
-
D.
Ramsgate
Ramsgate is a coastal resort town on South Africa’s KwaZulu-Natal South Coast, known for its beaches and holiday atmosphere.
-
E.
Eastbourne
Eastbourne is a seaside town and popular coastal resort on England’s south coast, known for its Victorian architecture, long promenade, and proximity to the chalk cliffs of Beachy Head.
- 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_69ca84defac48190abc1148804f184c1 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb2214a7c8190b516acf64e2b85db |
completed | April 2, 2026, 12:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1eacbc2348190bac1cc7f41a389b9 |
completed | April 5, 2026, 4:53 a.m. |
Created at: March 30, 2026, 8:30 p.m.