Triple
T30417107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Branch station |
E773786
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NJ Transit rail station |
C56472
|
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: NJ Transit rail station Context triple: [Long Branch station, instanceOf, NJ Transit rail 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.
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.
-
C.
Staten Island Railway station
A Staten Island Railway station is a designated stop along the Staten Island Railway line where trains load and unload passengers, typically featuring platforms, shelters, signage, and access to surrounding streets or transit connections.
-
D.
New York City Subway terminal
A New York City Subway terminal is a subway station where one or more train lines begin or end their scheduled service, typically featuring multiple tracks, crew facilities, and track arrangements for turning trains around.
-
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_69f22490b8b48190ab10c886a8d58c89 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:05 p.m.