Triple
T22238990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglia franchise |
E549669
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | passenger rail operating contract |
C43869
|
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: passenger rail operating contract Context triple: [Anglia franchise, instanceOf, passenger rail operating contract]
-
A.
passenger rail operating sector
The passenger rail operating sector comprises organizations and systems responsible for providing scheduled rail transport services for people, including train operations, customer service, safety management, and coordination with infrastructure owners and regulators.
-
B.
passenger rail service
Passenger rail service is a transportation system that operates trains to carry people between locations on a scheduled basis, typically offering various classes of comfort and amenities.
-
C.
intercity passenger rail project
An intercity passenger rail project is a coordinated planning, design, and construction effort to develop or improve rail infrastructure and services that transport people efficiently between cities over medium to long distances.
-
D.
operating rights agreement
chosen
An operating rights agreement is a contractual arrangement that grants a party the authority to operate, manage, or use specific assets, facilities, or services under defined terms, conditions, and limitations.
-
E.
passenger rail terminal
A passenger rail terminal is a dedicated facility where travelers board, disembark, and transfer between trains, supported by platforms, ticketing, waiting areas, and related passenger services.
- 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:38 p.m.