Triple
T5453622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westhoughton |
E122425
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Hindley |
E112385
|
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: Hindley | Statement: [Westhoughton, adjacentTo, Hindley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hindley Context triple: [Westhoughton, adjacentTo, Hindley]
-
A.
Hindley
chosen
Hindley is a railway station in Greater Manchester, England, serving the town of Hindley on the line between Wigan and Manchester.
-
B.
Heseltine
Heseltine is a surname most prominently associated with Michael Heseltine, a senior British Conservative politician and former Deputy Prime Minister.
-
C.
Kingsley
Kingsley is a small rural village and civil parish in East Hampshire, England.
-
D.
Halford
Halford is a small rural village in Shropshire, England, situated near the market town of Craven Arms.
-
E.
Lindley
Lindley refers to John Lindley, a prominent 19th-century English botanist known for his influential work in plant taxonomy and classification.
- 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd91e170f48190b47419b5e2ff71a4 |
completed | March 20, 2026, 6:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf4140248081908c7f42b91579a837 |
completed | March 22, 2026, 1:09 a.m. |
Created at: March 20, 2026, 2:08 p.m.