Triple
T12762157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YO! Bus |
E305021
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intercity bus service brand |
C16196
|
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: intercity bus service brand Context triple: [YO! Bus, instanceOf, intercity bus service brand]
-
A.
intercity coach service
An intercity coach service is a scheduled, long-distance bus transportation system that carries passengers between cities or towns, typically offering reserved seating, luggage capacity, and limited intermediate stops.
-
B.
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.
-
C.
transport brand
chosen
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.
-
D.
high-speed rail service brand
A high-speed rail service brand is a distinct identity and marketing concept that represents a specific provider’s fast, long-distance passenger train services, encompassing its name, visual design, service standards, and customer experience.
-
E.
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.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:28 p.m.