Triple
T10123265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keyworth, Nottinghamshire, England |
E223348
|
entity |
| Predicate | nearbySettlement |
P350
|
FINISHED |
| Object | Tollerton |
E608972
|
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: Tollerton | Statement: [Keyworth, Nottinghamshire, England, nearbySettlement, Tollerton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tollerton Context triple: [Keyworth, Nottinghamshire, England, nearbySettlement, Tollerton]
-
A.
Tollerton
chosen
Tollerton is a village in Nottinghamshire, England, situated near the city of Nottingham within the Rushcliffe borough.
-
B.
Twistleton
Twistleton is a fictional surname most notably associated with characters in P. G. Wodehouse’s humorous stories.
-
C.
Longton
Longton is a village in Lancashire, England, situated within the South Ribble district and known for its semi-rural character and commuter links to nearby Preston.
-
D.
Longton
Longton is a town in Stoke-on-Trent, Staffordshire, England, historically known as one of the six pottery towns of the region.
-
E.
Totton
Totton is a town in Hampshire, England, situated near the River Test on the outskirts of the New Forest and close to the city of Southampton.
- 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_69ca8422047c81909d66b717b8b18cf3 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd2ea7fe88190acb08d292a794638 |
completed | April 2, 2026, 2:22 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2cc52a4948190a7397c83912f3b15 |
completed | April 5, 2026, 8:55 p.m. |
Created at: March 30, 2026, 9:05 p.m.