Triple
T9008187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K |
E215397
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transit line designation |
C25452
|
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: public transit line designation Context triple: [K, instanceOf, public transit line designation]
-
A.
public transit line segment
A public transit line segment is a contiguous portion of a transit route between two consecutive stops or stations, characterized by its path, travel time, and operational attributes.
-
B.
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.
-
C.
subway line
A subway line is a fixed route within an urban rail transit system, consisting of a sequence of stations and tracks over which trains operate according to a scheduled service.
-
D.
bus rapid transit line
A bus rapid transit line is a high-capacity bus corridor that uses dedicated lanes, priority signaling, and streamlined stations to provide fast, reliable, rail-like transit service.
-
E.
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.
- 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_69ca83a2bf088190986ee7a8eb90407d |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 7:06 p.m.