Triple
T35616289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JR Central (Tokaido Shinkansen) |
E1029176
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway operator division |
C13555
|
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 operator division Context triple: [JR Central (Tokaido Shinkansen), instanceOf, railway operator division]
-
A.
railroad operating division
chosen
A railroad operating division is a geographically defined segment of a railway system managed as a unit for train operations, crew assignments, dispatching, and maintenance activities.
-
B.
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.
-
C.
operational railway route grouping
An operational railway route grouping is a structured collection of railway routes combined for coordinated planning, management, and control of train operations across a defined network segment.
-
D.
historical transit operating division
A historical transit operating division is an organizational unit within a past or legacy public transportation system responsible for managing and coordinating transit services, personnel, and resources within a specific geographic area or operational domain.
-
E.
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.
- 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_69f76e0709408190bbe322bf1707ef6b |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.