Triple
T34800388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greyhound |
E1003203
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transportation company 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: transportation company brand Context triple: [Greyhound, instanceOf, transportation company brand]
-
A.
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.
-
B.
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.
-
C.
transportation services company
A transportation services company is an organization that plans, manages, and operates the movement of people or goods using various modes of transport, such as road, rail, air, or sea, often providing logistics, scheduling, and support services.
-
D.
airline brand
An airline brand is the distinct identity and perception of an airline in the minds of customers, shaped by its visual design, service experience, reputation, and marketing communications.
-
E.
truck brand
A truck brand is a manufacturer or marque that designs, produces, and markets trucks under a distinct name, identity, and product lineup.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.