Triple
T14170975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canterbury District |
E351205
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Littlebourne |
E676557
|
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: Littlebourne | Statement: [Canterbury District, contains, Littlebourne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Littlebourne Context triple: [Canterbury District, contains, Littlebourne]
-
A.
Littlebourne
chosen
Littlebourne is a village and civil parish in Kent, England, situated near the city of Canterbury.
-
B.
Sittingbourne
Sittingbourne is an industrial and commuter town in southeast England, located in the county of Kent.
-
C.
Lavenham
Lavenham is a historic medieval wool town in Suffolk, England, renowned for its well-preserved timber-framed buildings and picturesque streets.
-
D.
Pangbourne
Pangbourne is a picturesque village on the River Thames in Berkshire, England, known for its literary associations and scenic rural charm.
-
E.
Wroxham
Wroxham is a village in Norfolk, England, widely regarded as the main boating and tourist centre of the Norfolk Broads.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61b472288190b4a271daa54aa6cd |
completed | April 14, 2026, 3:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcf808e6088190a607903be0f2adc7 |
completed | May 7, 2026, 8:37 p.m. |
Created at: April 10, 2026, 1:01 a.m.