Triple
T20897843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shoreham, Kent, England, United Kingdom |
E514586
|
entity |
| Predicate | nearbyVillage |
P4647
|
FINISHED |
| Object | Otford |
E178225
|
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: Otford | Statement: [Shoreham, Kent, England, United Kingdom, nearbyVillage, Otford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Otford Context triple: [Shoreham, Kent, England, United Kingdom, nearbyVillage, Otford]
-
A.
Otford
chosen
Otford is a historic village in Kent, England, known for its picturesque setting near Sevenoaks and remnants of an archbishop’s medieval palace.
-
B.
Yarrowford
Yarrowford is a small village in the Scottish Borders region of Scotland, situated in the Yarrow Valley near the River Yarrow.
-
C.
Wyndford
Wyndford is a residential neighborhood in the Maryhill area of Glasgow, Scotland, known for its post-war housing estates and close-knit community.
-
D.
Durford
Durford is a small settlement in West Sussex, England, situated in the countryside near the River Rother.
-
E.
Iford
Iford is a residential suburb within the Poole–Bournemouth urban area on the south coast of England.
- 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_69e0b4f7ebe48190952a85547a0f31a1 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6e8f826788190b11008cc94b2a4e4 |
completed | April 21, 2026, 3:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0918cefa2081909768f9923a96f209 |
completed | May 17, 2026, 1:24 a.m. |
Created at: April 16, 2026, 12:47 p.m.