Triple
T34685246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Primera Plus |
E890725
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | long-distance bus operator |
C29948
|
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: long-distance bus operator Context triple: [Primera Plus, instanceOf, long-distance bus operator]
-
A.
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.
-
B.
bus company group
chosen
A bus company group is an organization that owns, manages, and coordinates multiple bus operating companies to provide passenger transport services across various routes and regions.
-
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.
paratransit operator
A paratransit operator is a transportation service provider that offers flexible, demand-responsive rides—often door-to-door—for individuals whose disabilities or mobility limitations prevent them from using standard public transit.
-
E.
transport infrastructure operator
A transport infrastructure operator is an entity responsible for managing, maintaining, and regulating transportation networks and facilities such as roads, railways, ports, or airports to ensure safe and efficient movement of people and goods.
- 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:05 a.m.