Triple
T1927891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soundview Landing |
E40873
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | New York City Ferry terminal |
C6402
|
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: New York City Ferry terminal Context triple: [Soundview Landing, instanceOf, New York City Ferry terminal]
-
A.
bridge in New York City
A bridge in New York City is a large-scale transportation structure spanning waterways or land to connect boroughs and neighborhoods, supporting vehicular, rail, bicycle, and pedestrian traffic within the city’s dense urban environment.
-
B.
New York City Subway–railroad interchange
A New York City Subway–railroad interchange is a facility or location where subway lines physically connect with or provide direct transfer to mainline or commuter rail services, enabling passenger and sometimes equipment movement between the two systems.
-
C.
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.
-
D.
region of Manhattan
A region of Manhattan is a contiguous geographic area within the borough, defined by boundaries such as streets, avenues, or natural features, that shares common characteristics like land use, demographics, or cultural identity.
-
E.
ferry terminal
chosen
A ferry terminal is a designated facility where passengers and vehicles embark and disembark from ferries, typically providing ticketing, waiting areas, and docking infrastructure.
- 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_69a8864711648190b07bed24ed76258e |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:35 p.m.