Triple
T20023102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D-Zug |
E494910
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fast train service |
C31876
|
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: fast train service Context triple: [D-Zug, instanceOf, fast train service]
-
A.
rapid rail system
A rapid rail system is a high-speed, high-capacity railway network designed to transport large numbers of passengers quickly and efficiently between urban or regional destinations using dedicated tracks and frequent service.
-
B.
high-speed test train
A high-speed test train is a specialized railway vehicle designed to operate at very high velocities to evaluate, validate, and optimize track infrastructure, signaling systems, and rolling stock performance under extreme operating conditions.
-
C.
limited express train
chosen
A limited express train is a high-speed passenger service that stops only at major stations to provide faster travel between key destinations.
-
D.
rapid transit line
A rapid transit line is a high-capacity, high-frequency urban rail route operating on an exclusive or mostly separated right-of-way to provide fast, reliable public transportation between key areas of a city or metropolitan region.
-
E.
high-speed rail service brand
A high-speed rail service brand is a distinct identity and marketing concept that represents a specific provider’s fast, long-distance passenger train services, encompassing its name, visual design, service standards, and customer experience.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 3:35 p.m.