Triple
T19746093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TrawsCymru |
E474254
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | coach service network |
C5957
|
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: coach service network Context triple: [TrawsCymru, instanceOf, coach service network]
-
A.
transportation service
chosen
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.
-
B.
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.
-
C.
transport entrepreneur
A transport entrepreneur is an individual who identifies, develops, and manages innovative business opportunities in the movement of people or goods, leveraging logistics, technology, and market insights to create efficient and profitable transportation solutions.
-
D.
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.
-
E.
touring company
A touring company is an organization that plans, manages, and presents performances or events in multiple locations, often traveling with a cast, crew, and equipment to different venues.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:47 p.m.