Triple
T9975009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bury North |
E196304
|
entity |
| Predicate | hasBorderWith |
P224
|
FINISHED |
| Object | Bury South |
E283910
|
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: Bury South | Statement: [Bury North, hasBorderWith, Bury South]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bury South Context triple: [Bury North, hasBorderWith, Bury South]
-
A.
Bury South
chosen
Bury South is a UK parliamentary constituency in Greater Manchester, representing part of the Metropolitan Borough of Bury in the House of Commons.
-
B.
Bury North
Bury North is a UK parliamentary constituency in Greater Manchester that elects a Member of Parliament to the House of Commons.
-
C.
Bury Green
Bury Green is a small hamlet within the civil parish of Little Hadham in Hertfordshire, England.
-
D.
Bury
Bury is a town in North West England known for its traditional market, historic textile industry roots, and preserved East Lancashire Railway.
-
E.
Bury parish
Bury parish is an ecclesiastical parish centered on Bury Parish Church in the town of Bury, Greater Manchester, England.
- 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_69ca82eea2b88190a0e511d21a31f386 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb849da448190b826cb8fbf2eeb89 |
completed | April 2, 2026, 12:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d23ddcc01c8190bb00ac13cbbbb1fb |
completed | April 5, 2026, 10:47 a.m. |
Created at: March 30, 2026, 8:48 p.m.