Triple
T1861955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ancoats |
E34833
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Beswick |
E99814
|
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: Beswick | Statement: [Ancoats, adjacentTo, Beswick]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Beswick Context triple: [Ancoats, adjacentTo, Beswick]
-
A.
Beswick
chosen
Beswick is an inner-city district of Manchester, England, known for its industrial heritage and ongoing urban regeneration.
-
B.
Bakewell
Bakewell is a historic market town in Derbyshire, England, famed for its traditional Bakewell pudding and its picturesque setting in the Peak District.
-
C.
Highworth
Highworth is a historic market town in Wiltshire, England, known for its elevated position and traditional architecture.
-
D.
Buckland
Buckland is a small historic community located within the Bull Run Mountains region of northern Virginia.
-
E.
Buckland
Buckland is a small Inupiat community and city in northwestern Alaska situated along the Buckland River.
- 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_69a88600b2f88190bc09303e68ab517e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abb09e714881909cef0f7e77b5b3b9 |
completed | March 7, 2026, 4:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69add1d026748190a507872de85c908d |
completed | March 8, 2026, 7:45 p.m. |
Created at: March 4, 2026, 7:34 p.m.