Triple
T11931110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bury South |
E283910
|
entity |
| Predicate | containsArea |
P11790
|
FINISHED |
| Object | Unsworth |
E834858
|
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: Unsworth | Statement: [Bury South, containsArea, Unsworth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Unsworth Context triple: [Bury South, containsArea, Unsworth]
-
A.
Unsworth
chosen
Unsworth is a suburban area within the Metropolitan Borough of Bury in Greater Manchester, England.
-
B.
Ewhurst
Ewhurst is a rural village and civil parish in Surrey, England, known for its scenic countryside setting on the edge of the Surrey Hills.
-
C.
Elsworth
Elsworth is a surname and given name of English origin, historically associated with various places and families in England.
-
D.
Innsworth
Innsworth is a village in Gloucestershire, England, notable for its longstanding military presence and association with British and NATO command units.
-
E.
Riddlesworth
Riddlesworth is a small village in Norfolk, England, known for its rural setting and historic country house surroundings.
- 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90303a9a88190a4044e6310ba9b4b |
completed | April 10, 2026, 2:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f4406ee910819093c72738bfe3f92c |
completed | May 1, 2026, 5:55 a.m. |
Created at: April 8, 2026, 9:45 p.m.