Triple
T2310109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Lancashire Railway |
E51934
|
entity |
| Predicate | terminus |
P388
|
FINISHED |
| Object | Heywood |
E111924
|
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: Heywood | Statement: [East Lancashire Railway, terminus, Heywood]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heywood Context triple: [East Lancashire Railway, terminus, Heywood]
-
A.
Heywood
chosen
Heywood is a town in Greater Manchester, England, historically part of Lancashire and known for its industrial heritage.
-
B.
Morley
Morley is a town in West Yorkshire, England, situated between Leeds and Bradford within the Leeds City Council metropolitan area.
-
C.
Halstead
Halstead is a historic market town in the county of Essex in the East of England.
-
D.
Goodshaw
Goodshaw is a village and civil parish in Lancashire, England, situated within the Borough of Rossendale.
-
E.
Fleetwood
Fleetwood is a coastal town and historic port in Lancashire, England, known for its maritime heritage and role as a ferry and fishing hub.
- 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_69a88b0bb30c81908ded03b006d29387 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc6098ce88190ba2e987e6f0737ac |
completed | March 7, 2026, 6:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae7f3adc548190bb73d8bba58165fa |
completed | March 9, 2026, 8:05 a.m. |
Created at: March 4, 2026, 7:49 p.m.