Triple
T19496133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Marco Station |
E487775
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jacksonville Skyway station |
C42089
|
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: Jacksonville Skyway station Context triple: [San Marco Station, instanceOf, Jacksonville Skyway station]
-
A.
MARTA rail station
A MARTA rail station is a designated facility along the Metropolitan Atlanta Rapid Transit Authority’s rail network where passengers access, board, and transfer between trains and related transit services.
-
B.
AeroTrain station
An AeroTrain station is a designated facility where passengers board, disembark, and transfer between AeroTrains, providing platforms, ticketing, waiting areas, and related services for high-speed or automated airport rail transit.
-
C.
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.
-
D.
SunRail station
A SunRail station is a designated passenger facility along the SunRail commuter rail line that provides platforms, ticketing, and access services for boarding and alighting trains.
-
E.
Brightline station
A Brightline station is a dedicated passenger rail facility that serves as a boarding, alighting, and service hub for Brightline’s intercity trains, integrating ticketing, waiting areas, and connections to other local transportation 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:40 p.m.