Triple
T8322955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glastonbury |
E194878
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Pilton |
E492723
|
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: Pilton | Statement: [Glastonbury, near, Pilton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pilton Context triple: [Glastonbury, near, Pilton]
-
A.
Pilton
Pilton is a residential district in the north of Edinburgh, Scotland, known for its large housing estates and proximity to Granton.
-
B.
Pilton
chosen
Pilton is a historic suburb and former village now forming part of the town of Barnstaple in North Devon, England.
-
C.
Padiham
Padiham is a small town in Lancashire, England, situated near Burnley and known for its industrial heritage and proximity to the River Calder.
-
D.
Pittington
Pittington is a village in County Durham, England, known for its rural setting and proximity to historic estates such as Elemore Hall.
-
E.
Pilsley
Pilsley is a village in Derbyshire, England, known for its rural character and proximity to the Peak District.
- 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_69ca82e7a8a88190a32bb5cc0feb012d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f7cf49c8190b8440ff01926a66a |
completed | March 31, 2026, 8:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd95a8f18c819090f8e47061df1f55 |
completed | April 1, 2026, 10:01 p.m. |
Created at: March 30, 2026, 5:56 p.m.