Triple
T13030603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashford District |
E326428
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Bethersden |
E820397
|
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: Bethersden | Statement: [Ashford District, hasSettlement, Bethersden]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bethersden Context triple: [Ashford District, hasSettlement, Bethersden]
-
A.
Bethersden
chosen
Bethersden is a rural village and civil parish in the Ashford district of Kent, England, known for its historic buildings and traditional Kentish countryside setting.
-
B.
Hoddlesden
Hoddlesden is a small village in Lancashire, England, situated in a rural valley setting and historically associated with textile manufacturing.
-
C.
Bennetts End
Bennetts End is a residential area and suburb located within the county of Hertfordshire in England.
-
D.
Neasden
Neasden is a suburban area in northwest London, England, known for its residential character and proximity to major roads and rail links.
-
E.
Harpenden
Harpenden is a commuter town in southern England known for its green spaces and affluent residential character.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97efd18308190877b3269403b36e2 |
completed | April 10, 2026, 10:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6c123c36c8190b3fbf9cbb3b7ecf9 |
completed | May 3, 2026, 3:29 a.m. |
Created at: April 9, 2026, 8:54 p.m.