Triple
T14747423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunter line |
E346508
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional passenger railway service |
C75
|
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 passenger railway service Context triple: [Hunter line, instanceOf, regional passenger railway service]
-
A.
passenger rail service
chosen
Passenger rail service is a transportation system that operates trains to carry people between locations on a scheduled basis, typically offering various classes of comfort and amenities.
-
B.
regional rail service brand
A regional rail service brand is a distinct identity used to market and organize passenger train services within a specific geographic area, encompassing naming, visual design, and service characteristics.
-
C.
suburban commuter train
A suburban commuter train is a passenger rail service designed to transport people efficiently between residential suburbs and urban centers, typically operating on fixed schedules with frequent stops during peak travel times.
-
D.
regional bus service
A regional bus service is a public transportation system that operates scheduled bus routes connecting multiple towns or cities within a specific geographic area.
-
E.
passenger train
A passenger train is a rail vehicle or series of connected vehicles designed to transport people and their luggage between stations along a fixed route and schedule.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:30 a.m.