Triple
T10183960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brooklyn–Manhattan service |
E236860
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transit service pattern |
C20256
|
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: transit service pattern Context triple: [Brooklyn–Manhattan service, instanceOf, transit service pattern]
-
A.
railway line service pattern
chosen
A railway line service pattern defines the structured arrangement of train services over a route, including stopping sequences, frequencies, and service types that determine how trains operate along the line.
-
B.
public transit system
A public transit system is an organized network of shared transportation services—such as buses, trains, subways, and trams—designed to move large numbers of people efficiently within and between urban and regional areas.
-
C.
group of rapid transit lines
A group of rapid transit lines is a collection of interconnected high-capacity urban rail or metro routes that operate together as a coordinated network to provide frequent, efficient public transportation.
-
D.
metro service variant
A metro service variant is a specific version of a metro line’s operation, defined by a distinct pattern of stops, routing, frequency, or operating times that differentiates it from the standard service.
-
E.
public transport information system
A public transport information system is a software platform that collects, processes, and disseminates real-time and scheduled data about public transit services to passengers, operators, and other stakeholders.
- 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 9:12 p.m.