Triple
T26208911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Essex Thameside franchise |
E655430
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | passenger rail franchise |
C51251
|
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 franchise Context triple: [Essex Thameside franchise, instanceOf, passenger rail franchise]
-
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.
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.
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.
-
E.
commuter rail fare system
A commuter rail fare system is a structured method for calculating, collecting, and validating payments for passengers traveling on regional rail services, typically based on zones, distance, or time of travel.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
Created at: April 26, 2026, 8:51 p.m.