Triple
T5836753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eyam |
E129487
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Grindleford |
E161039
|
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: Grindleford | Statement: [Eyam, near, Grindleford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Grindleford Context triple: [Eyam, near, Grindleford]
-
A.
Grindleford
chosen
Grindleford is a village in the Derbyshire Peak District of England, known for its scenic countryside, walking trails, and proximity to popular climbing and hiking areas.
-
B.
Blyford
Blyford is a small rural village located in the English county of Suffolk.
-
C.
Sharneyford
Sharneyford is a small settlement in Lancashire, England, situated within the Rossendale Valley near the border with West Yorkshire.
-
D.
Belchford
Belchford is a small rural village in eastern England, situated within the scenic, rolling countryside of the Lincolnshire Wolds.
-
E.
Battisford
Battisford is a small rural village and civil parish located in the English county of Suffolk.
- 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_69c0084af79c81908af128ccc29983d0 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c034a48750819099ae917ae2b54e6d |
completed | March 22, 2026, 6:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c113464f7481909538a1f2ef05216c |
completed | March 23, 2026, 10:17 a.m. |
Created at: March 22, 2026, 3:54 p.m.