Triple
T28551659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campaign for Borders Rail |
E722903
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway campaign group |
C54246
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: railway campaign group Context triple: [Campaign for Borders Rail, instanceOf, railway campaign group]
-
A.
private rail initiative
A private rail initiative is a privately funded and operated railway project or service designed to develop, expand, or improve rail infrastructure and operations outside of direct government control.
-
B.
group of railway companies
A group of railway companies is an organized association of multiple rail transport operators that collaborate or are collectively managed to provide coordinated rail services, share resources, or pursue common commercial or regulatory interests.
-
C.
public railway
A public railway is a government- or publicly-owned rail transport system that provides scheduled passenger and/or freight services accessible to the general population, typically operating on standardized tracks and infrastructure.
-
D.
pre-grouping railway company
A pre-grouping railway company is a privately owned or regionally based railway operator in the United Kingdom that existed before the 1923 Railways Act consolidated most railways into the "Big Four" groups.
-
E.
suburban railway group
A suburban railway group is an organization or network that coordinates and operates rail services connecting a central city with its surrounding suburban areas, typically focusing on commuter transportation.
- F. None of above. chosen
Provenance (1 batch)
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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:43 a.m.