Triple
T10729922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alternate Concepts |
E253044
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transportation management company |
C4916
|
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 management company Context triple: [Alternate Concepts, instanceOf, transportation management company]
-
A.
transportation services company
chosen
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.
-
B.
transportation network company
A transportation network company is a business that uses digital platforms, typically mobile apps, to connect passengers with drivers who provide on-demand transportation services.
-
C.
transportation organization
A transportation organization is an entity that plans, manages, and operates systems or services that move people or goods from one location to another.
-
D.
corporate travel management company
A corporate travel management company is a specialized service provider that plans, books, and oversees business travel for organizations to optimize cost, compliance, and traveler experience.
-
E.
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.
- 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_69d6aa5d8be481909a43218b2bfdbe95 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:14 p.m.