Triple
T995190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manchester–Chester line |
E21479
|
entity |
| Predicate | via |
P5680
|
FINISHED |
| Object | Frodsham |
E117078
|
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: Frodsham | Statement: [Manchester–Chester line, via, Frodsham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Frodsham Context triple: [Manchester–Chester line, via, Frodsham]
-
A.
Sandbach
Sandbach is a historic market town in Cheshire, England, noted for its Saxon crosses and traditional town centre.
-
B.
Knutsford
Knutsford is a historic market town in Cheshire, England, known for its picturesque streets, affluent character, and literary associations with Elizabeth Gaskell.
-
C.
Nantwich
Nantwich is a historic market town in northwest England known for its well-preserved Tudor and Georgian architecture and long association with the salt industry.
-
D.
Northwich
Northwich is a historic market and industrial town in Cheshire, England, traditionally known for its salt mining and chemical industries.
-
E.
Frodsham railway station
chosen
Frodsham railway station is a local rail stop in Frodsham, Cheshire, England, providing passenger services on routes between Manchester and Chester.
- 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4c75de88190bf7fec7a053f7a90 |
completed | March 1, 2026, 9:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac5995ad6c8190a324094151442bce |
completed | March 7, 2026, 5 p.m. |
Created at: March 1, 2026, 7:41 p.m.