Triple
T1415191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buxton |
E31898
|
entity |
| Predicate | postTown |
P2711
|
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: [Buxton, postTown, BUXTON]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BUXTON Context triple: [Buxton, postTown, BUXTON]
-
A.
Buxton
chosen
Buxton is a historic spa town in Derbyshire, England, renowned for its thermal mineral springs and Georgian architecture.
-
B.
Branxton
Branxton is a small rural town in New South Wales, Australia, situated in the Hunter Region and known as a gateway to the Hunter Valley wine country.
-
C.
Buellton
Buellton is a small city in California’s Santa Ynez Valley known for its wineries, roadside attractions, and role as a gateway to the Santa Barbara wine country.
-
D.
Bankton
Bankton is a residential area forming part of the town of Livingston in West Lothian, Scotland.
-
E.
Ashbourne
Ashbourne is a historic market town in Derbyshire, England, known for its traditional architecture and annual Royal Shrovetide Football match.
- 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c402b1648190b87802d9beb2712e |
completed | March 1, 2026, 10:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ace5812abc819091894509e9d6bd77 |
completed | March 8, 2026, 2:57 a.m. |
Created at: March 1, 2026, 7:59 p.m.