Triple

T2263355
Position Surface form Disambiguated ID Type / Status
Subject Nottingham railway station E50087 entity
Predicate connectsTo P845 FINISHED
Object Lincoln railway station E97318 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: Lincoln railway station | Statement: [Nottingham railway station, connectsTo, Lincoln railway station]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lincoln railway station
Context triple: [Nottingham railway station, connectsTo, Lincoln railway station]
  • A. Lincoln railway station chosen
    Lincoln railway station is the main rail transport hub serving the historic cathedral city of Lincoln in Lincolnshire, England.
  • B. Lincoln station
    Lincoln station is a commuter rail stop in Lincoln, Massachusetts, serving passengers on the MBTA's Fitchburg Line.
  • C. Butler station
    Butler station is a small MBTA light rail stop on Boston’s historic Mattapan trolley line in the Dorchester/Mattapan area.
  • D. Bradford station
    Bradford station is a commuter rail station in Haverhill, Massachusetts, serving MBTA's Haverhill Line.
  • E. Lancaster Station
    Lancaster Station is an Amtrak passenger rail station in Lancaster, Pennsylvania, serving intercity and regional trains along the Keystone Corridor.
  • 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_69a88b01e0048190ba96431b5f990ba9 completed March 4, 2026, 7:41 p.m.
NER Named-entity recognition batch_69abc18d7fc08190851765683d1b8092 completed March 7, 2026, 6:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae71cfd3b08190988474aa0fa985fe completed March 9, 2026, 7:08 a.m.
Created at: March 4, 2026, 7:48 p.m.