Triple
T14246962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armidale railway station |
E353159
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional rail terminus |
C10600
|
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: regional rail terminus Context triple: [Armidale railway station, instanceOf, regional rail terminus]
-
A.
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.
-
B.
railway bridge terminus
A railway bridge terminus is the endpoint of a rail line where tracks transition from or onto a bridge structure, often incorporating platforms, signaling, and facilities for train arrival, departure, and turnaround.
-
C.
terminal station
chosen
A terminal station is a railway or transit station where a line or service ends, requiring trains or vehicles to reverse direction or terminate their routes.
-
D.
narrow-gauge railway terminus
A narrow-gauge railway terminus is the end station or final stopping point on a railway line that uses tracks of narrower width than the standard gauge, where trains begin or conclude their journeys and related operations are managed.
-
E.
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.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:08 a.m.