Triple
T962840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derbyshire |
E20773
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Bakewell |
E30940
|
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: Bakewell | Statement: [Derbyshire, containsSettlement, Bakewell]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bakewell Context triple: [Derbyshire, containsSettlement, Bakewell]
-
A.
Bakewell
chosen
Bakewell is a historic market town in Derbyshire, England, famed for its traditional Bakewell pudding and its picturesque setting in the Peak District.
-
B.
Bolsover
Bolsover is a historic market town in England best known for its hilltop Bolsover Castle and its location within the county of Derbyshire.
-
C.
Epsom
Epsom is a market town in Surrey, England, best known for the Epsom Downs Racecourse and the famous Epsom Derby horse race.
-
D.
Banbury
Banbury is a historic market town in Oxfordshire, England, known for its medieval cross, canal-side setting, and association with the traditional Banbury cake.
-
E.
Yorkton
Yorkton is a small city in southeastern Saskatchewan, Canada, known as a regional hub for agriculture and services.
- 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_69a493b21f2881908132dcf45dcd2f36 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b416cf4c8190bd685227db25fb53 |
completed | March 1, 2026, 9:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac17034cf48190bca513891cfcc444 |
completed | March 7, 2026, 12:16 p.m. |
Created at: March 1, 2026, 7:40 p.m.