Triple
T6819201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JR Lines at Kanda |
E156853
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway service group |
C14575
|
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 service group Context triple: [JR Lines at Kanda, instanceOf, railway service group]
-
A.
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.
-
B.
group of railway companies
chosen
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.
-
C.
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.
-
D.
pre-grouping railway company
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.
-
E.
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.
- 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_69c688298a288190af3f285d57f76bbe |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:17 p.m.