Triple
T22143556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APT-P |
E547226
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high-speed train prototype |
C36733
|
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: high-speed train prototype Context triple: [APT-P, instanceOf, high-speed train prototype]
-
A.
high-speed test train
chosen
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.
-
B.
proposed high-speed ground transportation system
A proposed high-speed ground transportation system is a conceptual network of advanced vehicles, infrastructure, and control technologies designed to move passengers or freight rapidly and efficiently between destinations along dedicated terrestrial corridors.
-
C.
rapid transit vehicle
A rapid transit vehicle is a high-capacity, electrically powered rail car or train designed to provide frequent, fast, and reliable urban or suburban passenger transportation on dedicated or grade-separated tracks.
-
D.
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.
-
E.
InterCityExpress variant
An InterCityExpress variant is a specific model or configuration of high-speed ICE train designed for particular routes, capacities, or service requirements within an intercity rail network.
- 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_69e11e3a95d88190a3bd80d9471976c3 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:32 p.m.