Triple
T36300628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haddonfield PATCO station |
E893499
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | PATCO Speedline station |
C63540
|
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: PATCO Speedline station Context triple: [Haddonfield PATCO station, instanceOf, PATCO Speedline station]
-
A.
Newark Light Rail station
A Newark Light Rail station is a designated stop or terminal along the Newark Light Rail system where passengers can board, alight, and transfer between light rail vehicles and other modes of transit.
-
B.
SEPTA Norristown High Speed Line station
A SEPTA Norristown High Speed Line station is a passenger transit stop along the Norristown High Speed Line that provides platforms, access facilities, and services for boarding and alighting high-speed light rail vehicles.
-
C.
Hudson–Bergen Light Rail station
A Hudson–Bergen Light Rail station is a designated stop or terminal along New Jersey’s Hudson–Bergen Light Rail system that provides platforms, facilities, and access points for passengers boarding, alighting, and transferring between light rail services and other modes of transportation.
-
D.
Trinity Railway Express station
A Trinity Railway Express station is a designated passenger rail facility along the Trinity Railway Express commuter line that provides platforms, ticketing access, and related services for boarding and alighting trains.
-
E.
Tri-Rail station
A Tri-Rail station is a designated passenger rail facility along South Florida’s Tri-Rail commuter line where trains stop to allow riders to board, alight, and access related transit services.
- 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_69f76e4a61f0819084a2b68dbbb4efc6 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.