Triple
T10694732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rivington Pike |
E252104
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Horwich |
E35592
|
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: Horwich | Statement: [Rivington Pike, near, Horwich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Horwich Context triple: [Rivington Pike, near, Horwich]
-
A.
Horwich
chosen
Horwich is a town in Greater Manchester, England, historically notable as a major railway engineering and locomotive works centre.
-
B.
Wallisdown
Wallisdown is a suburban area of Bournemouth in Dorset, England, known for hosting higher education campuses and residential neighborhoods.
-
C.
Wallington
Wallington is a suburban town in the London Borough of Sutton, known for its residential character, grammar schools, and green spaces in south London, England.
-
D.
Wallington
Wallington is a small rural village in the North Hertfordshire district of England, known for its historic buildings and traditional countryside character.
-
E.
Killingworth
Killingworth is a village in North Tyneside, England, historically notable for its early coal mining and railway engineering associations.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fd39c3788190bb7cd0acf8b6efdd |
completed | April 9, 2026, 1:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d998cfeb748190bfff06534d83cf97 |
completed | April 11, 2026, 12:41 a.m. |
Created at: April 8, 2026, 9:11 p.m.