Triple
T1738579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North British Railway |
E37977
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Scottish railway company |
C2005
|
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: Scottish railway company Context triple: [North British Railway, instanceOf, Scottish railway company]
-
A.
private railway company
A private railway company is a non-governmental business entity that owns, operates, or manages rail transport services for passengers and/or freight, typically for profit under regulatory oversight.
-
B.
railway holding company
A railway holding company is a parent corporation that owns and controls one or more railway operating or infrastructure companies, managing their strategic direction and financial interests without necessarily running day-to-day train operations itself.
-
C.
national railway company
A national railway company is a state-owned or state-controlled organization responsible for operating and managing a country's primary passenger and freight rail transport services and infrastructure.
-
D.
railway company of Russia
A railway company of Russia is an organization that owns, operates, or manages rail transport infrastructure and services within the Russian Federation, including passenger and freight operations.
-
E.
pre-grouping railway company
chosen
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.
- F. None of above.
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_69a8861cc6ac8190ac0b2e31ccf62851 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:30 p.m.