Triple
T16812482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silver Line (Washington Metro) stations |
E408648
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Washington Metro stations |
C37875
|
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: Washington Metro stations Context triple: [Silver Line (Washington Metro) stations, instanceOf, Washington Metro stations]
-
A.
Baltimore Metro SubwayLink station
A Baltimore Metro SubwayLink station is a designated transit facility where passengers can board, alight, and transfer between Metro SubwayLink trains and other transportation modes within the Baltimore metropolitan area.
-
B.
METRO Green Line station
A METRO Green Line station is a designated stop along the METRO Green Line light rail system where passengers can board, alight, and transfer between trains and other modes of transit.
-
C.
Purple Line station
A Purple Line station is a designated stop or terminal along a transit system's Purple Line where passengers can board, alight, and transfer between services.
-
D.
MARC station
A MARC station is a designated passenger rail stop along the Maryland Area Regional Commuter (MARC) train network, providing boarding, alighting, and related services for regional commuters.
-
E.
Miami-Dade Transit Metrorail station
A Miami-Dade Transit Metrorail station is a designated passenger facility along the Metrorail rapid transit system in Miami-Dade County that provides platforms, access points, and related services for boarding, alighting, and transferring between trains and other transit modes.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
Created at: April 10, 2026, 5:23 a.m.