Triple
T26914519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rapi:t |
E677481
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | train service brand styling |
C19103
|
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: train service brand styling Context triple: [rapi:t, instanceOf, train service brand styling]
-
A.
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.
-
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.
railway livery
chosen
A railway livery is the distinctive color scheme, markings, and branding applied to trains and related rolling stock to identify a railway company or service.
-
D.
rail freight brand
A rail freight brand is the distinct identity, including name, visual design, reputation, and service promise, that differentiates a company providing cargo transportation by rail from its competitors.
-
E.
railroad brand
A railroad brand is the distinct identity, image, and reputation associated with a railway company, encompassing its name, logo, visual design, service quality, and public perception.
- 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 6:03 a.m.