Triple
T30470930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEPTA NHSL |
E775289
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high-speed line |
C51991
|
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 line Context triple: [SEPTA NHSL, instanceOf, high-speed line]
-
A.
high-speed railway
chosen
A high-speed railway is a rail transport system designed for trains that operate at significantly higher speeds than traditional rail services, typically on specially built or upgraded tracks, to provide fast, efficient, and reliable long-distance passenger travel.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
rapid transit line segment
A rapid transit line segment is a contiguous portion of a rapid transit route between two defined points (such as stations, junctions, or terminals) that carries high-frequency, high-capacity passenger rail service.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:11 p.m.