Triple
T18392597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East End |
E449772
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Swerford |
—
|
NE NERFINISHED |
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: Swerford | Statement: [East End, locatedNear, Swerford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Swerford Context triple: [East End, locatedNear, Swerford]
-
A.
Swerford
chosen
Swerford is a small rural village in Oxfordshire, England, known for its historic stone cottages and picturesque countryside setting.
-
B.
Baverstock
Baverstock is a small rural hamlet in Wiltshire, England, known for its historic church and tranquil countryside setting.
-
C.
Havercroft
Havercroft is a village in West Yorkshire, England, situated within the metropolitan borough of the City of Wakefield.
-
D.
Bardwell
Bardwell is a small rural village and civil parish in the county of Suffolk in eastern England.
-
E.
Snodland
Snodland is a small town in Kent, England, known historically for its cement and paper industries and its location between Maidstone and Rochester.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e518435cf481908393c1eb2b4ba659 |
completed | April 19, 2026, 6 p.m. |
Created at: April 10, 2026, 10:46 a.m.