Triple
T3900119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U11 (peak-hour service variant) |
E90466
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | supplementary peak-hour service |
C13511
|
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: supplementary peak-hour service Context triple: [U11 (peak-hour service variant), instanceOf, supplementary peak-hour service]
-
A.
rush-hour service
chosen
Rush-hour service is a transportation or customer service schedule that provides increased capacity or frequency during peak demand periods to accommodate higher user volumes efficiently.
-
B.
limited-stop bus service
A limited-stop bus service is a transit route that only stops at selected key locations rather than every stop, reducing travel time for longer-distance passengers.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69aed95d315881908cbf1bf4a7215fbf |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.