Triple
T822530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newcastle Interchange |
E17780
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | light rail stop |
C2851
|
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: light rail stop Context triple: [Newcastle Interchange, instanceOf, light rail stop]
-
A.
light-rail station
chosen
A light-rail station is a designated facility where light-rail vehicles stop to allow passengers to board, alight, and transfer between services, typically featuring platforms, shelters, signage, and ticketing amenities.
-
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.
commuter rail station
A commuter rail station is a designated facility where passengers board and alight regional trains that connect suburbs or outlying areas with urban centers, typically offering platforms, ticketing, and basic passenger amenities.
-
D.
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.
-
E.
light rail vehicle
A light rail vehicle is a rail-based transit vehicle designed for urban and suburban passenger service, typically operating on dedicated or shared tracks with frequent stops and moderate capacity.
- 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.