Triple
T6963205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Capital Connect |
E161423
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former British rail franchise operator |
C20589
|
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: former British rail franchise operator Context triple: [First Capital Connect, instanceOf, former British rail franchise operator]
-
A.
former British Rail sector
A former British Rail sector is an organizational division that once managed specific types of rail services or geographic areas within the state-owned British Rail system before its restructuring and privatization.
-
B.
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.
-
C.
rail transport company
A rail transport company is an organization that owns, operates, or manages trains and railway infrastructure to provide freight and/or passenger transportation services.
-
D.
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.
-
E.
transport infrastructure operator
A transport infrastructure operator is an entity responsible for managing, maintaining, and regulating transportation networks and facilities such as roads, railways, ports, or airports to ensure safe and efficient movement of people and goods.
- 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_69c68853cff881908439d488924a8283 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:30 p.m.