Triple
T9217148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DASH |
E221269
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bus service brand |
C7634
|
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: bus service brand Context triple: [DASH, instanceOf, bus service brand]
-
A.
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.
-
B.
public transit brand
chosen
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.
-
C.
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.
-
D.
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.
-
E.
public transport service feature
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.
- 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_69ca83eae42c8190a0ea9e040710a277 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:27 p.m.