Triple
T21219445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bedford railway station |
E522924
|
entity |
| Predicate | connectsTo |
P845
|
FINISHED |
| Object | Corby |
—
|
NE NERFINISHED |
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: Corby | Statement: [Bedford railway station, connectsTo, Corby]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Corby Context triple: [Bedford railway station, connectsTo, Corby]
-
A.
Corby
chosen
Corby is a town in Northamptonshire, England, known for its steel industry heritage and significant Scottish community.
-
B.
Yorkton
Yorkton is a small city in southeastern Saskatchewan, Canada, known as a regional hub for agriculture and services.
-
C.
Scunthorpe
Scunthorpe is an industrial town in North Lincolnshire, England, historically known for its steel production.
-
D.
Huddersfield
Huddersfield is a large market town in West Yorkshire, England, known for its Victorian architecture, university, and role in the Industrial Revolution.
-
E.
Bradford
Bradford is a masculine given name of Old English origin, traditionally meaning "broad ford" and used both as a first name and surname.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69e0b511ed84819099b449b4a111085c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73476d93481909c6c99dcc0b16123 |
completed | April 21, 2026, 8:25 a.m. |
Created at: April 16, 2026, 3:43 p.m.