Triple
T14853475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wardley |
E349289
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Pendlebury |
E10842
|
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: Pendlebury | Statement: [Wardley, adjacentTo, Pendlebury]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pendlebury Context triple: [Wardley, adjacentTo, Pendlebury]
-
A.
Pendlebury
chosen
Pendlebury is a suburban area in the City of Salford, Greater Manchester, England, historically known for its coal mining and textile industries.
-
B.
Wrenbury
Wrenbury is a rural village and civil parish in Cheshire, England, known for its historic church, canalside setting, and traditional English countryside character.
-
C.
Bredenbury
Bredenbury is a small rural village and civil parish in Herefordshire, England, known for its countryside setting near the market town of Bromyard.
-
D.
Peddle Thorp
Peddle Thorp is an Australian architectural firm known for designing a wide range of commercial, residential, and public buildings.
-
E.
Samlesbury
Samlesbury is a village in Lancashire, England, known for its historic Samlesbury Hall and its location near the River Ribble.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded44318f0819080b6c599f2d3474f |
completed | April 14, 2026, 11:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe6506ace48190819504b93f575660 |
completed | May 8, 2026, 10:34 p.m. |
Created at: April 10, 2026, 1:54 a.m.