Triple
T19516925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 700 |
E488300
|
entity |
| Predicate | route |
P5619
|
FINISHED |
| Object | Bedford to Brighton |
—
|
NE NERFINISHED |
How this triple was built (3 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: Bedford to Brighton | Statement: [British Rail Class 700, route, Bedford to Brighton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bedford to Brighton Context triple: [British Rail Class 700, route, Bedford to Brighton]
-
A.
London to Brighton
London to Brighton is a major commuter and intercity rail route in southern England linking the capital with the seaside city of Brighton on the south coast.
-
B.
Cambridge–Brighton route
The Cambridge–Brighton route is a cross-London commuter and regional rail service linking Cambridge in the north with Brighton on the south coast via central London.
-
C.
Brighton–Eastbourne–Hastings coastal route
The Brighton–Eastbourne–Hastings coastal route is a key railway line in East Sussex, England, linking major seaside towns along the south coast and forming an important part of the regional commuter and leisure rail network.
-
D.
London to Worthing corridor
The London to Worthing corridor is a major north–south transport axis in southeast England linking the capital with the south coast through a chain of towns and strategic routes.
-
E.
London Charing Cross – Hastings
London Charing Cross – Hastings is a mainline rail service in Southeast England linking central London with the coastal town of Hastings via intermediate stations in Kent and East Sussex.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Bedford to Brighton Target entity description: Bedford to Brighton is a major north–south commuter and regional rail corridor in southern England linking Bedfordshire with the south coast via central London.
-
A.
London to Brighton
London to Brighton is a major commuter and intercity rail route in southern England linking the capital with the seaside city of Brighton on the south coast.
-
B.
Cambridge–Brighton route
chosen
The Cambridge–Brighton route is a cross-London commuter and regional rail service linking Cambridge in the north with Brighton on the south coast via central London.
-
C.
Brighton–Eastbourne–Hastings coastal route
The Brighton–Eastbourne–Hastings coastal route is a key railway line in East Sussex, England, linking major seaside towns along the south coast and forming an important part of the regional commuter and leisure rail network.
-
D.
London to Worthing corridor
The London to Worthing corridor is a major north–south transport axis in southeast England linking the capital with the south coast through a chain of towns and strategic routes.
-
E.
London Charing Cross – Hastings
London Charing Cross – Hastings is a mainline rail service in Southeast England linking central London with the coastal town of Hastings via intermediate stations in Kent and East Sussex.
- F. None of above.
Provenance (2 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6359ca7648190804c4d655170fda3 |
completed | April 20, 2026, 2:18 p.m. |
Created at: April 10, 2026, 1:40 p.m.