Triple
T14862486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wyoming (via Gosford) – implied access |
E349530
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transport access description |
C15962
|
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: public transport access description Context triple: [Wyoming (via Gosford) – implied access, instanceOf, public transport access description]
-
A.
public transport service feature
chosen
A public transport service feature is a specific characteristic, function, or amenity of a public transportation offering that affects how passengers access, experience, and evaluate the service.
-
B.
public transport information system
A public transport information system is a software platform that collects, processes, and disseminates real-time and scheduled data about public transit services to passengers, operators, and other stakeholders.
-
C.
transportation service
A transportation service is a system or business that moves people or goods from one location to another using various modes of transport under defined schedules, routes, and conditions.
-
D.
public transit board
A public transit board is a governing body responsible for overseeing, setting policy for, and making strategic decisions about a region’s public transportation system.
-
E.
transport model
A transport model is a conceptual or mathematical representation used to simulate and analyze the movement of people, goods, or resources across a network or spatial system under various conditions and constraints.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:54 a.m.