Triple
T947649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atherton line |
E20447
|
entity |
| Predicate | terminus |
P388
|
FINISHED |
| Object | Southport |
E68739
|
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: Southport | Statement: [Atherton line, terminus, Southport]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Southport Context triple: [Atherton line, terminus, Southport]
-
A.
Southport
chosen
Southport is a seaside town and popular tourist resort on the Irish Sea coast in North West England.
-
B.
Southport
Southport is a major coastal suburb and business hub of the City of Gold Coast in Queensland, Australia, known for its waterfront, shopping, and commercial precincts.
-
C.
Workington
Workington is a coastal town and port on the west coast of England, historically known for its steel and coal industries and situated at the mouth of the River Derwent.
-
D.
Maghull
Maghull is a suburban town in Merseyside, England, situated to the north of Liverpool and functioning largely as a residential commuter area.
-
E.
Hartlepool
Hartlepool is a coastal town in County Durham, England, known historically for its shipbuilding and maritime heritage.
- 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_69a493b0f2fc81908cd227480a5356a1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3be19448190a8863fce3d152430 |
completed | March 1, 2026, 9:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac5e9b74e481908c7d8256bd180d73 |
completed | March 7, 2026, 5:21 p.m. |
Created at: March 1, 2026, 7:40 p.m.