Triple
T26040963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broughton |
E647687
|
entity |
| Predicate | servedByHistoricRailway |
P782
|
FINISHED |
| Object | Symington, Biggar and Broughton Railway |
—
|
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: Symington, Biggar and Broughton Railway | Statement: [Broughton, servedByHistoricRailway, Symington, Biggar and Broughton Railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByHistoricRailway Context triple: [Broughton, servedByHistoricRailway, Symington, Biggar and Broughton Railway]
-
A.
servedByRailroad
chosen
Indicates that a location or facility is provided with transportation or service by a railroad line or company.
-
B.
formerRailOperator
Indicates that an entity previously operated a rail service or railway system but no longer does so.
-
C.
formerRailwayLine
Indicates that a railway line previously existed in the past but is no longer in operation or has been decommissioned.
-
D.
servedRailroadsIn
Indicates that an individual or entity provided service or worked in an official capacity for one or more specified railroad companies.
-
E.
followsFormerRailroad
Indicates that something is aligned with or traces the route of a former railroad line.
- F. None of above.
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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 22, 2026, 9:08 a.m.