Triple
T13505692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Folkestone and Hythe District |
E321009
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Capel-le-Ferne |
E326409
|
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: Capel-le-Ferne | Statement: [Folkestone and Hythe District, contains, Capel-le-Ferne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Capel-le-Ferne Context triple: [Folkestone and Hythe District, contains, Capel-le-Ferne]
-
A.
Capel-le-Ferne
chosen
Capel-le-Ferne is a coastal village in Kent, England, known for its clifftop location above the White Cliffs and its Battle of Britain memorial.
-
B.
Capel
Capel is a rural village and civil parish in Kent, England, situated within the Borough of Tunbridge Wells.
-
C.
Capel
Capel is a small town in Western Australia’s South West region, situated between Bunbury and Busselton and known for its proximity to coastal areas and surrounding forests.
-
D.
Capel
Capel is a rural village and civil parish in the Mole Valley district of Surrey, England.
-
E.
Penthièvre
Penthièvre is a historic region in Brittany, France, traditionally associated with a ducal title and noble lineage.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf8259a08190ada13c4a3078f07d |
completed | April 12, 2026, 2:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7548bc188819090773db66b0103a1 |
completed | May 3, 2026, 1:58 p.m. |
Created at: April 9, 2026, 9:43 p.m.