Triple
T14940679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All Saints Church, Lydd |
E372517
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Lydd |
E372517
|
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: Lydd | Statement: [All Saints Church, Lydd, locatedIn, Lydd]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lydd Context triple: [All Saints Church, Lydd, locatedIn, Lydd]
-
A.
Lydd
chosen
Lydd is a small historic town in Kent, England, situated on the Romney Marsh and known for its medieval church and proximity to the English Channel.
-
B.
Esher
Esher is a suburban town in the borough of Elmbridge in Surrey, England, known for its affluent residential character and proximity to London.
-
C.
Basildon
Basildon is a large town in Essex, England, known as a post-war new town and a major commercial and residential centre within the East of England.
-
D.
Hainault
Hainault is a suburban area in northeast London, England, known for its residential character and proximity to Hainault Forest Country Park.
-
E.
Swanscombe
Swanscombe is a town in Kent, England, known for its archaeological significance and proximity to major transport links including Ebbsfleet International railway station.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded64a2f24819099b21566756668a2 |
completed | April 15, 2026, 12:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe7e929f3881908560b8428e72327d |
completed | May 9, 2026, 12:23 a.m. |
Created at: April 10, 2026, 2:38 a.m.