Triple
T12314550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oyster Ticket Stops |
E293567
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transport retail network |
C10593
|
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 retail network Context triple: [Oyster Ticket Stops, instanceOf, public transport retail network]
-
A.
transportation network company
A transportation network company is a business that uses digital platforms, typically mobile apps, to connect passengers with drivers who provide on-demand transportation services.
-
B.
public transit customer service facility network
chosen
A public transit customer service facility network is a coordinated system of physical and/or virtual locations where transit users can obtain information, purchase or manage fare products, resolve service issues, and access support related to public transportation services.
-
C.
public transit brand
A public transit brand is the cohesive identity—encompassing name, visuals, messaging, and perceived values—that distinguishes a transit agency’s services and shapes how riders recognize, trust, and experience the system.
-
D.
transport brand
A transport brand is a conceptual class representing a company or entity that provides transportation services or products, characterized by attributes like name, logo, service types, and reputation, and behaviors such as marketing, service delivery, and customer support.
-
E.
automotive retailer
An automotive retailer is a business that sells new and/or used vehicles, related financing, and support services directly to consumers.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:53 p.m.