Triple
T18908286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pardubice railway region |
E462525
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rail transport district |
C41312
|
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: rail transport district Context triple: [Pardubice railway region, instanceOf, rail transport district]
-
A.
rail transit
Rail transit is a public transportation system that moves passengers or freight along fixed steel tracks using trains, subways, trams, or light rail vehicles, typically in urban or intercity corridors.
-
B.
rapid transit division
A rapid transit division is an organizational unit within a transportation agency responsible for planning, operating, and maintaining high-frequency, high-capacity urban rail or bus rapid transit services.
-
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.
commuter rail line
A commuter rail line is a passenger train service that operates on fixed tracks and schedules to connect suburban or outlying areas with a central city, primarily serving daily work and school commuters.
-
E.
light rail transit line
A light rail transit line is a fixed-route urban or suburban rail corridor using electrically powered, relatively low-capacity trains that operate on dedicated or semi-exclusive tracks to provide frequent, short- to medium-distance passenger service.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:58 a.m.