Triple
T30292135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro Liner |
E770407
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transportation 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: public transportation service brand Context triple: [Metro Liner, instanceOf, public transportation service brand]
-
A.
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.
-
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.
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.
-
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.
mass transit operator
A mass transit operator is an entity responsible for managing, coordinating, and providing public transportation services such as buses, trains, or subways within a specific region or network.
- 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:47 p.m.