Triple
T13030278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woodnesborough |
E326417
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Eastry |
E330672
|
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: Eastry | Statement: [Woodnesborough, near, Eastry]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eastry Context triple: [Woodnesborough, near, Eastry]
-
A.
Eastry
chosen
Eastry is a historic village and civil parish in Kent, England, known for its rural character and proximity to the coastal town of Deal.
-
B.
Hellingly
Hellingly is a village and civil parish in East Sussex, England, known for its rural character and historic parish church.
-
C.
Tealby
Tealby is a picturesque rural village in eastern England, known for its traditional stone cottages and scenic setting within the Lincolnshire countryside.
-
D.
Grindon
Grindon is a residential suburb of Sunderland in the Wearside area of North East England.
-
E.
Ewhurst
Ewhurst is a rural village and civil parish in Surrey, England, known for its scenic countryside setting on the edge of the Surrey Hills.
- 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.