Triple
T19246691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shepway |
E481277
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Lyminge |
E927661
|
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: Lyminge | Statement: [Shepway, containsSettlement, Lyminge]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lyminge Context triple: [Shepway, containsSettlement, Lyminge]
-
A.
Lyminge
chosen
Lyminge is a historic village in Kent, England, notable for its early medieval Anglo-Saxon archaeological remains and religious significance.
-
B.
Wimblebury
Wimblebury is a small village in Staffordshire, England, situated near the town of Hednesford within the Cannock Chase area.
-
C.
Hensingham
Hensingham is a residential suburb of Whitehaven in Cumbria, England, known for its local community facilities and proximity to the town’s centre.
-
D.
Yorton
Yorton is a small rural village in Shropshire, England, known for its modest railway station on the Crewe–Shrewsbury line.
-
E.
Waldringfield
Waldringfield is a small riverside village in eastern England known for its scenic setting on the River Deben and sailing activities.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb2daacc8190b8af99dee51f238d |
completed | April 20, 2026, 10:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0705e0e9208190ab6857bdc61ad22e |
completed | May 15, 2026, 11:39 a.m. |
Created at: April 10, 2026, 1:27 p.m.