Triple
T7023169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Hall Hotel, Buxton |
E162878
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Buxton |
E31898
|
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: Buxton | Statement: [Old Hall Hotel, Buxton, locatedIn, Buxton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Buxton Context triple: [Old Hall Hotel, Buxton, locatedIn, Buxton]
-
A.
Buxton
chosen
Buxton is a historic spa town in Derbyshire, England, renowned for its thermal mineral springs and Georgian architecture.
-
B.
Buxton
Buxton is a village in Norfolk, England, known for its rural setting and historic association with the River Bure.
-
C.
Bexton
Bexton is a small rural area in Cheshire, England, situated on the outskirts of the town of Knutsford.
-
D.
Biddulph
Biddulph is a small town in Staffordshire, England, known historically for its coal mining and rural surroundings.
-
E.
Rothbury
Rothbury is a historic market town and civil parish in Northumberland, England, situated on the River Coquet and known as a gateway to the Northumberland National Park.
- 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_69c6885b26248190a857541e3d10e299 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e1edf3608190b7ba0bfb85710e97 |
completed | March 27, 2026, 8 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c82754e9248190b86b05b61a4ae23c |
completed | March 28, 2026, 7:09 p.m. |
Created at: March 27, 2026, 2:35 p.m.