Triple
T13629793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Outer Circle |
E325683
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subway service pattern |
C14534
|
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: subway service pattern Context triple: [Outer Circle, instanceOf, subway service pattern]
-
A.
railway line service pattern
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.
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.
-
C.
New York City Subway service designation
A New York City Subway service designation is a letter, number, or symbol that identifies a specific subway route, indicating its line, terminals, and general service pattern for riders.
-
D.
metro service variant
chosen
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.
rapid transit network
A rapid transit network is an integrated system of high-capacity, high-frequency urban rail or bus lines designed to move large numbers of passengers quickly and efficiently across a metropolitan area.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:51 p.m.