Triple
T38665111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keihin Kyūkō (Tokyo–Yokohama express) |
E940433
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Japanese private railway operator |
C5965
|
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: Japanese private railway operator Context triple: [Keihin Kyūkō (Tokyo–Yokohama express), instanceOf, Japanese private railway operator]
-
A.
national railway company
A national railway company is a state-owned or state-controlled organization responsible for operating and managing a country's primary passenger and freight rail transport services and infrastructure.
-
B.
private railway company
chosen
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.
Tokyo Metropolitan Bureau of Transportation
The Tokyo Metropolitan Bureau of Transportation is the governmental agency responsible for operating and managing Tokyo’s public transportation services, including subways, trams, and buses within the Tokyo Metropolis.
-
D.
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.
-
E.
railway company of Russia
A railway company of Russia is an organization that owns, operates, or manages rail transport infrastructure and services within the Russian Federation, including passenger and freight operations.
- 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_69f76edfde348190bf6529d9f49ecd62 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:33 p.m.