Triple
T822527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newcastle Interchange |
E17780
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transport interchange |
C82
|
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: transport interchange Context triple: [Newcastle Interchange, instanceOf, transport interchange]
-
A.
transport hub
chosen
A transport hub is a central location where multiple modes or routes of transportation intersect, enabling the efficient transfer of passengers or goods between them.
-
B.
rapid transit station
A rapid transit station is a designated facility where passengers board, alight, and transfer between high-frequency urban rail or metro services, typically featuring platforms, ticketing areas, and access to surrounding streets or other transport modes.
-
C.
train station
A train station is a designated facility where trains regularly stop to pick up and drop off passengers and sometimes freight, typically featuring platforms, ticketing services, and waiting areas.
-
D.
public transit system
A public transit system is an organized network of shared transportation services—such as buses, trains, subways, and trams—designed to move large numbers of people efficiently within and between urban and regional areas.
-
E.
public transportation infrastructure
Public transportation infrastructure encompasses the physical and organizational systems—such as buses, trains, stations, tracks, and supporting facilities—that enable the efficient movement of people via shared transit services.
- 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_69a4937bcaac8190a322524ac6f45a5a |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:38 p.m.